Installed Bind8, now acting weird

kevin9 · 03-10-2006, 04:59 PM

I just installed the latest version of Bind8 on a Redhat9 box, I haven't configured anything but as soon as I installed it I could no longer use nslookup. It worked fine before, but now it just spits out:

*** Can't find server name for address X: Non-existent host/domain
*** Default servers are not available

Seems I figured out it does this on any nameserver that doesn’t reverse resolve.

Is there anything I can switch to fix this? Never seen it before.

Thanks

ARC1450 · 03-10-2006, 07:23 PM

Post up your config, if you would. Is it a simple caching server, forwarding server, or what?

kevin9 · 03-10-2006, 08:30 PM

Well, that's the weird part. I have not configed bind yet, it is not running.

Just after installing bind8, nslookup started acting weird. I am using the hosts nameservers, and while they are still functioning over all and everything else seems to working.. nslookup now gives me that error. I played with adding other nameservers, and the error comes from using any nameserver in resolv.conf that doesnt reverse resolve.

If nothing else is broken, I guess it isn't really a problem. Was more curious if there is a way to fix that than anything. And wondering if anything else is broken like nslookup that I am have not found out yet

Thanks

gilead · 03-10-2006, 09:42 PM

Does your /etc/resolv.conf file have anything apart from:

Code:

nameserver 192.168.1.55

Where 192.168.1.55 is your ISP's name server?

kevin9 · 03-10-2006, 09:48 PM

Nope. Just nameserver and the IPs

Nothing was changed in that file, the only thing that changed on the server was bind8. nslookup worked for everything, after make install of bind8, it quit..

gilead · 03-10-2006, 10:01 PM

It seems you've already correctly identified the problem - the fact that the domain does not reverse resolve, or that it has no PTR data. It's a name server config problem issue, not yours by the look of it. At http://www.unix.org.ua/orelly/networ...m#AUTOID-12708 is a description of a problem that sounds like yours:

Quote:

The "nonexistent domain" means that the name 3.249.249.192.in-addr.arpa doesn't exist. In other words, nslookup couldn't find the name for 192.249.249.3, its name server host. But didn't we just say that nslookup doesn't look up anything when it starts up? In the configuration presented before, nslookup didn't look up anything, but that's not a rule. If you create a resolv.conf that includes nameserver lines, nslookup looks up the address in order to get the name server's name. In the preceding example, there is a name server running on 192.249.249.3, but it said there is no PTR data for the address 192.249.249.3. Obviously, this name server's data is messed up, at least for the 249.249.192.in-addr.arpa zone.

kevin9 · 03-10-2006, 11:05 PM

Thanks for the info, so I guess it is just nslookup broken. Not that big of a deal. Kind of annoying, but guess nothing from my end that I can do about it.

Thanks again

gilead · 03-10-2006, 11:21 PM

No problem - I couldn't find anywhere that said if it had changed in bind 9, so I'm not recommending upgrading to find out