On Monday 17 February 2003 18:11, Paul Makepeace wrote:

> It seems that looking up the address (`host srl.org`) returns the A
> record without consulting the nameservers, presumably since it's
> registered with an A record by dint of being a whois-known nameserver. I
> didn't realise the gTLD servers did that. What a pain in the arse.
>
> penderel:~$ ns srl.org | perl -ne '/\S+$/ && print `host srl.org $&`'
> srl.org                 A       208.44.199.253
> srl.org                 A       208.44.199.253
> srl.org                 A       208.44.199.253
> penderel:~$ host srl.org
> srl.org                 A       64.81.251.171
> penderel:~$

right ... what you have here is an unwanted glue record:

in the dig stuff below you will see the line:

srl.org.                172800  IN      A       64.81.251.171

that is coming directly from the .org root server.  the query is never 
referred to your nameservers as the .org root server is able to give an 
authoratative answer ...  and  helpfully it is 4 days TTL .. so at best it 
will be friday before it gets sorted :)

AFAIK the only way to get rid of these is to make a request to the registrar 
to do it manually, as it is rarely possible using the sh1tty web forms.

(ask a certain dave hodg about the fun we had with a glue record for www.blah)



##########################################################

[robin@workstation robin]$ dig @E5.NSTLD.COM srl.org a +norecurse

; <<>> DiG 9.1.3 <<>> @E5.NSTLD.COM srl.org a
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39381
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 0

;; QUESTION SECTION:
;srl.org.                       IN      A

;; ANSWER SECTION:
srl.org.                172800  IN      A       64.81.251.171

;; AUTHORITY SECTION:
srl.org.                86400   IN      NS      ns3.realprogrammers.com.
srl.org.                86400   IN      NS      ns2.realprogrammers.com.
srl.org.                86400   IN      NS      ns1.realprogrammers.com.

#############################################################

-- 
Robin Szemeti

Reply via email to