DNS

[atul.kaggarwal]

Hi, I am getting below message in syslog:

*********************syslog******************

Dec 4 17:10:53 mumbs3 named[16872]: lame server resolving 'jhainc.com' (in 'jhainc.com'?): 207.69.188.201#53
Dec 4 17:10:53 mumbs3 named[16872]: lame server resolving 'hasenbeck.net' (in 'hasenbeck.NET'?): 62.153.123.31#53
Dec 4 17:10:54 mumbs3 named[16872]: lame server resolving 'hasenbeck.net' (in 'hasenbeck.NET'?): 62.153.122.14#53
***********************************************
here please let me know whats the meaning of these errors specially this Lame Server. Also my DNS server frequently stop resolving sites and when i kill the named process and then restart process then only it start working. So please let me know what would be the issue.

[Peter Godron]

Atul,
please see:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=181208

Please also read:
http://forums1.itrc.hp.com/service/forums/helptips.do?#33 on how to reward any useful answers given to your questions.

So far you have not awarded any points !

[Frank W Hansen_CEX]

A DNS server which is supposed to be authoritative for a zone, but isnt.

If you see something like this

Dec 4 17:10:53 mumbs3 named[16872]: lame server resolving 'jhainc.com' (in 'jhainc.com'?): 207.69.188.201#53

in your BIND logs, then BIND has queried a lame server. In this case, the server is mentioned as being authoritative somewhere for the zone, but when BIND queries it, it discovers that is not authoritative, and logs that message.

If you are an administrator and got tired from all these messages in your logs, you can easily disable this "lame server" logging once and for all. Just add the following directive in your /etc/named.conf (or whereever your named.conf is on your machine):

logging {
category lame-servers { null; };

};

[atul.kaggarwal]

Thanks for information, but can you let me know why my DNS server stop responding and after restarting start working. Currently around 400 domains are hosted on that server.