Lame server: whose problem?

Jim Reid jim at rfc1035.com
Mon Jan 24 18:23:32 UTC 2000


>>>>> "Kevin" == Kevin D Quitt <KQuitt at IEEInc.com> writes:

    Kevin> Windows NT 4, SP6a, Bind 4.9.7.  I'm getting the following
    Kevin> events: Lame server on '189.138.37.211.in-addr.arpa' (in
    Kevin> '138.37.211.IN-ADDR.ARPA'?): [203.245.15.2].53
    Kevin> 'nis.hitel.net': learnt (A=128.8.10.90,NS=134.75.30.1)

    Kevin> Is this caused by something I have wrong in my setup?

No, not unless you're responsible for the name servers for the reverse
zone 138.37.211.IN-ADDR.ARPA (nis.hitel.net and nis2.hitel.net). These
two servers are supposed to be authoritative for that domain, but
they're not. Hence the "lame delegation" errors. If you care about
this, take it up with the DNS administrator for this zone or the owner
of net 211.37.138.

BTW BIND4 is dead. You should be running the current version, 8.2.2P5.



More information about the bind-users mailing list