named only lintening on 127.0.0.0 interface

Barry Margolin barmar at bbnplanet.com
Thu Mar 16 23:57:34 UTC 2000


In article <00b601bf8ded$35646240$0300a8c0 at develop.fastec.com.br>,
Fabio Aleixo Santos <fabio at fastec.com.br> wrote:
>I am setting up a secondary DNS server  on a linux slackware 3.5 box with
>kernel 2.0.36.
>I have other machine running OK as primary dns,  but the in the secondary it
>seems that the named is only listening to the local loopback interface.

Is it possible that your startup scripts are starting named before the
network interfaces have been configured?  If so, you'll need to move the
named startup to later in the process.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.



More information about the bind-users mailing list