Re: strange named behavior in 3.4-STABLE

1999-12-25 Thread Mike Harding
It's an issue with the new version of Bind - 8.2.2 seems to ping the network on startup, whereas the previous version did not. I haven't found a way around this behaviour but that doesn't mean there isn't one. I noticed this behaviour when I was an early 8.2 adapter via the ports. - Mike H.

Re: strange named behavior in 3.4-STABLE

1999-12-25 Thread Marcin Cieslak
I guess the problem is that some utility attempts do use DNS quite early, like sendmail(1). Most probably, you messed up your /etc/hosts file, if not - you may use "DontProbeInterfaces" sendmail option. -- << Marcin Cieslak // [EMAIL PROTECTED] >> -

Re: strange named behavior in 3.4-STABLE

1999-12-25 Thread Jim Weeks
Your problem is most likely sendmail. It will always issue a request when booting and if you have the standard "sendmail -bd -q30m" set in /etc/rc.conf it will cause dial up every 30 minutes. You could change the command to "sendmail -bd" to stop the 30 minute dialing, but it will still dial du

strange named behavior in 3.4-STABLE

1999-12-25 Thread Lev Serebryakov
Hi, All! I've upgraded from 3.3-STABLE to 3.4-STABLE and notice strange thing: I have ``named'' run on my machine, which have only dial-up Internet connection. I have ``ppp -nat -auto provider'' run too. My named have configured to be primary NS in my network (domain is not regi