Differences between version 4 and predecessor to the previous major change of LameServer.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Wednesday, November 24, 2004 4:15:35 pm | by MikeBeattie | Revert |
| Older page: | version 1 | Last edited on Sunday, August 10, 2003 4:00:17 pm | by JamesBraid | Revert |
@@ -1,9 +1,12 @@
A DNS server which is supposed to be authoritative for a zone, but isnt.
If you see something like this:
-Aug 7 00:57:37 colo named[827]: lame server resolving '98.96-27.40.119.62.in-addr.arpa' (in '96-27.40.119.62.in-addr.arpa'?): 62.119.40.115#53
+
Aug 7 00:57:37 colo named[
[827]: lame server resolving '98.96-27.40.119.62.in-addr.arpa' (in '96-27.40.119.62.in-addr.arpa'?): 62.119.40.115#53
in your BIND logs, then BIND has queried a lame server. In this case, 62.119.40.115 is mentioned as being authoritative somewhere for the zone 98.96-27.40.119.62.in-addr.arpa, but when BIND queries it, it discovers that 62.119.40.115 is not authoritative, and logs that message. The [SysAdmin] at the other end needs to get a clue and fix his DNS.
See the [Weekly Lame Delegation report|http://www.cymru.com/DNS/lame.html]
+
+----
+CategoryDns
