9 May
2005
9 May
'05
9:11 p.m.
I think that I have answered my own question. I replaced the nameserver 0.0.0.0 line with the ip address that the locally running named is configured to listen on and the problem went away.
Jim
-- *** e-mail is not a secure channel *** mailto:byrnejb.<token>@harte-lyne.ca James B. Byrne Harte & Lyne Limited vox: +1 905 561 1241 9 Brockley Drive fax: +1 905 561 0757 Hamilton, Ontario <token> = hal Canada L8E 3C3