wrong ip being resolved on google dns

72 views
Skip to first unread message

dan.p...@gmail.com

unread,
Dec 9, 2019, 10:21:52 AM12/9/19
to public-dns-discuss
I have a strange issue with some public dns, like google

;; ANSWER SECTION:
navo.ro.                13071   IN      A       89.44.124.30


nameservers are resolved correctly:
dig navo.ro @8.8.8.8 in ns
;; ANSWER SECTION:
navo.ro.                20519   IN      NS      ns3.speed-gazduire.ro.
navo.ro.                20519   IN      NS      ns4.speed-gazduire.ro.
navo.ro.                20519   IN      NS      ns5.speed-gazduire.ro.


each of the ns3,4,5 resolve the domain correclty:
;; ANSWER SECTION:
navo.ro.                14400   IN      A       89.44.124.105


Even level3 dns resolve it correctly:

;; ANSWER SECTION:
navo.ro.                14400   IN      A       89.44.124.105



the domain was last week on 89.44.124.30, but was moved on saturday on 89.44.124.105
TTL was 14400

Now where does 8.8.8.8 get the result from?

Wesley Peng

unread,
Dec 9, 2019, 9:17:22 PM12/9/19
to public-dn...@googlegroups.com
Hi

on 2019/12/9 22:58, dan.p...@gmail.com wrote:
> dig navo.ro @8.8.8.8
> ;; ANSWER SECTION:
> navo.ro.                13071   IN      A       89.44.124.30
>

It's due to stale cache.
Now the resolution seems correct.

$ dig navo.ro @8.8.8.8

; <<>> DiG 9.11.3-1ubuntu1-Ubuntu <<>> navo.ro @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2742
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;navo.ro. IN A

;; ANSWER SECTION:
navo.ro. 14399 IN A 89.44.124.105

;; Query time: 288 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Dec 10 10:16:09 HKT 2019
;; MSG SIZE rcvd: 52

regards.

Dan Padure

unread,
Dec 13, 2019, 9:30:15 AM12/13/19
to public-dns-discuss


On Tuesday, 10 December 2019 04:17:22 UTC+2, Wesley Peng wrote:


It's due to stale cache.
Now the resolution seems correct.


Well, for navo.ro indeed it's ok
but I have such problems for other domains:  
ipadgr.ro.              13750   IN      A       93.115.53.24
 
some dns servers from the 8.8.8.8 cluster respond ok
ipadgr.ro.              13752   IN      A       89.44.124.35

But some don't

How can this be, after more than 1 week since the change?



Alex Dupuy

unread,
Dec 13, 2019, 10:54:55 AM12/13/19
to public-dns-discuss
One of your name servers (ns2.twin-hosting.ro, 82.79.19.22) is returning the old address 93.115.53.24. It appears to have a very old (October?) version of your zone file:

3.124.215.71 returns ns3.speed-gazduire.ro. cpanel.twin-hosting.ro. 2019121201 3600 1800 1209600 86400
63.35.50.52 returns ns3.speed-gazduire.ro. cpanel.twin-hosting.ro. 2019121201 3600 1800 1209600 86400
188.240.231.159 returns ns3.speed-gazduire.ro. cpanel.twin-hosting.ro. 2019121201 3600 1800 1209600 86400
82.79.19.22 returns ns3.speed-gazduire.ro. dan.padure.gmail.com. 2019101705 3600 1800 1209600 86400


Dan Padure

unread,
Dec 13, 2019, 6:23:05 PM12/13/19
to public-dns-discuss
Alex, I had a feeling that one of the older ns could have something to do with it.
 In October we replaced 2 nameserver from the cluster.  But we changed the dns records for ns3

I don't understand how and why was 82.79.19.22 still being queried about these domains??  Since ns3, ns4, ns5 point to the new ips.
and all the domains have these 3 nameservers listed.

How did you figured it out?

we turned off the old nameserver now. Even though it should not have mattered if it was on or off...
Reply all
Reply to author
Forward
0 new messages