[BlueOnyx:06397] Re: Disappearing DNS

[Alan Kline]

Hallelujah! Thank you (again!) Chris! And thank you as well to the other 
gentlemen who offered advice and suggestions. All are greatly appreciated.

For everyone else...Chris worked very diligently a week or so ago fixing 
a problem that was entirely my doing (don't ask!). I've worked with 
Chris and his staff now for about 5 years or so, and the service has 
always been above top notch...

And I also hope that the problem and solution that Chris found may be 
useful to others...

Now, to catch up on a day's worth of email that's flowing in... ;)



On 1/25/2011 10:00 PM, Chris Gebhardt - VIRTBIZ Internet wrote:
> Alan Kline wrote:
>> Hi Chris,
>>
>> Yes, it's the server we worked on last week, and DNS is enabled. The
>> nslookup returns:
>>
>> [root at www /]# nslookup
>>   >  server xxx.67.248.202
>> Default server: xxx.67.248.202
>> Address: xxx.67.248.202#53
>>   >  snugglebunny.us
>> ;; connection timed out; no servers could be reached
>
> I found Alan's issue and wanted to pass it along in case it helps anyone
> in the future.
>
> The server had an entry in the reverse DNS (aka "network" dropdown in
> the "Edit Primary Services" screen) for the 0.0.0.127.in-addr.arpa zone.
>      I'm not sure why that popped up in there, but I believe it may have
> done so after importing from the old server.   The problem is that BIND
> (or "named") chokes on that and then fails to start.  So nameservice was
> never really running.
>
> The solution is to "Remove Records" so that the zone gets wiped out,
> BIND is restarted, and the problem is solved.
>
> I didn't happen to have shell access to the system this go-round, but
> when I've seen this behavior before it's pretty easy to restart BIND
> from the CLI (service named restart) and if it fails it's pretty good
> about reporting why.   That can greatly speed TTR (Time To Resolution)!
>