Why is this old address still being given out?
Answered Thu, 30 May 2002> Here's my problem.
>
> Our company has two name servers:
>
> iticket51.billettluka.com (81.0.148.2)
> iticket50.billettluka.com (81.0.148.1)
>
> (I know having them on the same subnet is bad... but I just work here.
> These decisions are out of my hands.)
>
> Here is the zone file for billettluka.com
>
> refresh = 900
> retry = 600
> expire = 3600
> default TTL = 600
>
> If I type:
>
> nslookup iticket50.billettluka.com iticket51.billettluka.com
>
> The correct IP is returned (81.0.148.1)
>
> But if I type:
>
> nslookup iticket50.billettluka.com someother.ns.com
>
> An incorrect IP is returned (80.0.148.1) This was probably a typo in
> the zone file that has now been corrected.
>
> Q. Why are name servers still serving up this old info. (We are talking
> days now...that I can confirm that the zone file states the correct IP).
> Shouldn't it have timed out ages ago?
No, because that A record is registered with the gTLD name servers:
$ dig @a.gtld-servers.net. iticket50.billettluka.com.
; <<>> DiG 9.2.1 <<>> @a.gtld-servers.net. iticket50.billettluka.com.
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59245
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;iticket50.billettluka.com. IN A
;; ANSWER SECTION:
iticket50.billettluka.com. 172800 IN A 80.0.148.1
You need to ask your registrar (Active ISP ASA) to change the registration for iticket50.billettluka.com.
> Q. This problem is causing my secondary to appear dead. If there is
> nothing I can do, how long can I expect to wait?
Once you change the registration, it'll take a day or two to change.
cricket