Differences between current version and predecessor to the previous major change of LameServer.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 6 Last edited on Friday, April 14, 2006 3:21:36 am by AndreiKoptev
Older page: version 4 Last edited on Wednesday, November 24, 2004 4:15:35 pm by MikeBeattie Revert
@@ -4,9 +4,20 @@
  Aug 7 00:57:37 colo named[[827]: lame server resolving '' (in ''?): 
 in your BIND logs, then BIND has queried a lame server. In this case, is mentioned as being authoritative somewhere for the zone, but when BIND queries it, it discovers that is not authoritative, and logs that message. The [SysAdmin] at the other end needs to get a clue and fix his DNS. 
+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; };  
+That's it.  
 See the [Weekly Lame Delegation report|]