Google DNS cache not updating?

[Erik Jan Hofstede]

Hi,

I'm having some strange issues. It seems Google DNS is not updating
it's cache properly. Doing 'dig antagonist.nl soa @8.8.8.8' 10 ~ 20
times is giving me different results.
Correct result:
=============================================================
; <<>> DiG 9.7.0-P1 <<>> antagonist.nl soa @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39934
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;antagonist.nl. IN SOA

;; ANSWER SECTION:
antagonist.nl. 180 IN SOA ns1.antagonist.nl.
hostmaster.antagonist.nl. 2012031500 180 3600 1209600 86400
=============================================================

Wrong result:
=============================================================
; <<>> DiG 9.7.0-P1 <<>> antagonist.nl soa @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49216
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;antagonist.nl. IN SOA

;; ANSWER SECTION:
antagonist.nl. 180 IN SOA ns1.antagonist.nl. root.antagonist.nl.
2012030907 180 3600 1209600 86400

;; Query time: 84 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Mar 15 16:07:04 2012
;; MSG SIZE rcvd: 76
=============================================================

The wrong result seems to be a very old cached soa of a nameserver
we're not using anymore for 6 days now.

Anybody got an idea of what's going on?

[Yunhong Gu]

Hello,

There are 3 name servers for "antagonist.nl", one of them "ns2.antagonist.net" does not have the correct glue record at the delegation point (net. name servers). It is still pointed to 83.96.139.140/ns2.webhostingserver.nl, although its own name server has the new IP 178.22.60.37. Due to this error, your query to antagonist.nl/soa may return different results - in case the resolvers happen to use ns2.antagonist.net, you are likely to see the old record.

Please ask the service provider to fix this.

Yunhong

--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to
public-dns-disc...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================

[Erik Jan Hofstede]

Thanks! Strange I didn't notice that, checked it (and others too)
serveral times.

[ag security]

I have a similar issue for paveamerica.com.. It is hosted with CloudFlare and many other root caches are updated but not google and it causes all kinds of problems