I'm hoping that someone here can explain a very strange issue. I recently had to configure a new internal nameserver after the old server smoked itself. All is working, however, when using nslookup, the response looks like:
bitstream# nslookup bitstream
Server: bitstream.aablueprint.com
Address: 0.0.0.0
Name: bitstream.aablueprint.com
Address: 192.168.1.1
BTW, this is asking the nameserver what it's name is. Notice the first address reported for the Server. I cannot figure out why it keeps saying 0.0.0.0, but the same issue is breaking rndc. I have checked all the zone files, and experimented with removing several of them from the conf file - like all the reverse lookup files. I expected this to cause an error out, but the response was the exact same thing as above!
anyone?
--
Jay
bitstream# nslookup bitstream
Server: bitstream.aablueprint.com
Address: 0.0.0.0
Name: bitstream.aablueprint.com
Address: 192.168.1.1
BTW, this is asking the nameserver what it's name is. Notice the first address reported for the Server. I cannot figure out why it keeps saying 0.0.0.0, but the same issue is breaking rndc. I have checked all the zone files, and experimented with removing several of them from the conf file - like all the reverse lookup files. I expected this to cause an error out, but the response was the exact same thing as above!
anyone?
--
Jay
