Doesn't listen on LAN 192.168.

Danny Mayer mayer at gis.net
Mon Nov 4 14:43:01 UTC 2002


At 11:31 PM 10/31/02, Simon Waters wrote:

>David Gillespey wrote:
> >
> > BIND9.2.2rc1 doesn't listening on IPv4 interface TCP/IP Interface 2,
> > 192.168.0.155#53 when computer is restarted, only listens on 127.0.0.1,
> > until bind is manually restarted then works fine serving the LAN. No errors
> > in event viewer.

You didn't say whether or not this is on NT/W2K, but from the wording
I'd say it is. Are you saying that at the time the O/S is rebooted that
the log shows that it sees the interface but doesn't respond to it? When
this happens what does netstat -an say? Does it show a listener on port
53 on that interface?

I've never seen or heard of this before. What O/S and version are you
running?

Danny

>If it were Unix/Linux I'd say schedule the starting of BIND
>further down the list of services to start. Normally on starting
>it binds to all available IPv4 interfaces, so my first guess is
>it is starting before the interface is available.
>
>Depending on permissions the *nix versions also rescan and
>rebind to all interfaces at regular interfaces (1 hour by
>default), you could shrink this interval (interface-interval) if
>it works on NT, but it is a bit of a "hack".



More information about the bind-users mailing list