Search Again: Re: :Lame Name server From: Len Conrad Date: Wednesday, October 9, 2002 Time: 8:27:20 pm >I just got a DNS report from www.DNSreport.com and it warned me that I >don't have "Glue at root" and the failed items were "Lame Nameservers" >for 211.5.1.219. The reverse authority for that ip is in the ;;authority section here: # dig -x 211.5.1.219 ; <<>> DiG 8.3 <<>> -x ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 ;; QUERY SECTION: ;; 219.1.5.211.in-addr.arpa, type = ANY, class = IN ;; ANSWER SECTION: 219.1.5.211.in-addr.arpa. 1D IN PTR dns12.dion.ne.jp. ;; AUTHORITY SECTION: 1.5.211.in-addr.arpa. 1D IN NS dns0.dion.ne.jp. 1.5.211.in-addr.arpa. 1D IN NS dns2.dion.ne.jp. 1.5.211.in-addr.arpa. 1D IN NS dns10.dion.ne.jp. 1.5.211.in-addr.arpa. 1D IN NS ns1.neweb.ne.jp. Without knowing your domain name, kinda hard to help you. A lame NS is one that has been delegated with authority for a zone but is not answering authoritatively (or not at all) for that zone. >It also said I didn't have a "Reverse DNS entries for MX records". For your MX hostname's ip, there was no reverse zone delegation, or if there was reverse delegation, there was no PTR for that ip. When you put in the PTR record for the ip of the MX hostname, make sure the PTR and A records "match". Len

Messages In This Thread: :Lame Name server by David Campbell on Oct 9, 2002 at 6:43:24 pm Re: :Lame Name server by Men & Mice Support on Oct 9, 2002 at 8:18:14 pm Re: :Lame Name server by Len Conrad on Oct 9, 2002 at 8:27:20 pm Re: :Lame Name server by David Campbell on Oct 9, 2002 at 8:36:37 pm Re: :Lame Name server by Len Conrad on Oct 9, 2002 at 8:47:32 pm Re: :Lame Name server by Men & Mice Support on Oct 10, 2002 at 12:16:00 pm Re: :Lame Name server by David Campbell on Oct 10, 2002 at 8:57:45 pm