listening on

Barry Margolin barmar at genuity.net
Wed Apr 26 21:53:00 UTC 2000


In article <8e7l02$p6q$1 at news.IAEhv.nl>,
Diederich Kroeske <kroeske at iae.nl> wrote:
>In my intranet i have installed a DNS server that will lookup local names
>and forwards all unresolved names to
>the dns of my isp. I have the problem that the DNS servers listens on ippp0
>instead of eth0. ( I see 'listening on [192.168.0.10].53 (ippp0)) in
>/var/log/messages but I expect eth0. I also can't resolve addresses from
>within my local network, the machine immediately connects to the internet.
>When I'm connected to the internet the eth0 is replaced by ippp0 so
>everything looks fine then. Any suggestions?

Unless you have the "listen-on" option in your named.conf, named should
automatically listen on all interfaces that are available.  Every hour it
will scan the interface list to add and remove interfaces that it listens
on as necessary (the frequency is configurable via the "interface-interval"
option).  If it's not listening on eth0 when it starts up, it implies that
this interface wasn't configured at that time (perhaps you need to change
the order of things in your system startup script, so that the eth0
interface is configured before starting named).

-- 
Barry Margolin, barmar at genuity.net
Genuity, 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