named listens to 127.0.0.1 but not IP address

Kevin Darcy kcd at daimlerchrysler.com
Mon Oct 16 20:36:54 UTC 2000


gman at linuxrox.com wrote:

> the place I work for is just about to hit over 250 computers..
> So we need to add IP addresses. So we decided just to renumber
> the network from a Class 192.168.2.0 to a B Class 128.1.0.0...
>
> Now th problem I am having is when I configure the ethernet port
> on either solaris 7 or linux with a subnet of 255.255.0.0...
> Using nslookup breaks.. I can still do a nslookup againist the
> localhost IP address but not on the IP address of the
> ethernet port...
>
> Is this a problem with bind itself or do I just need more sleep..
> Any ideas??.. I've already  added the listen-on statement to make
> sure it would bind to the IP address. ANd I used netstat -na to
> see if it would listening to port 53 and it was... but nothing..
>
> when I switch back to a C Class, it works again.. ideas??

It's not clear to me whether you *just* changed the subnet mask or you actually
changed the IP address of the ethernet interface. If you changed the IP address,
then unless you have reverse lookup set up for the new address, nslookup is going
to bogusly fail. Real lookup tools like "dig" however, should still work,
regardless of whether the nameserver address can be reverse-resolved or not.

If all you changed was the subnet mask, then I'd say this is probably a deeper
networking problem rather than a DNS/BIND problem _per_se_.

Oh, and don't use an illegal B class. Use another slice of 192.168/16, as Mathias
already suggested.


- Kevin





More information about the bind-users mailing list