Chat Online
Support

Forum

A place for Dynadot and community experts alike to ask questions, share ideas, and more.
Some Domains not updating
1/31/2014 05:59
I recently changed hosting plans with the same company, but they used different dns servers.  I've had the new settings for some time, but I got some automated warnings today about sites down.  Several of the domains seem to be resolving to the wrong servers.



Example: wondible.com

DyanDot IP lookup has the right values::

Registry Name Servers
dns.pair.com
ns7.ns0.com

Zone Name Servers
dns.pair.com
ns7.ns0.com




But dig on my local computer has some old servers:

dig wondible.com

; <<>> DiG 9.8.3-P1 <<>> wondible.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20004
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;wondible.com.                  IN      A

;; ANSWER SECTION:
wondible.com.           3600    IN      A       209.68.26.128

;; AUTHORITY SECTION:
wondible.com.           3600    IN      NS      ns7.ns0.com.
wondible.com.           3600    IN      NS      ns522.pair.com.

;; Query time: 21 msec
;; SERVER: 64.135.192.8#53(64.135.192.8)
;; WHEN: Fri Jan 31 07:51:38 2014
;; MSG SIZE  rcvd: 93
Reply Quote
2/11/2014 15:56
As we discussed over chat, all your settings look good.  Looks like you were able to resolve the issue since your sites are online now. :)
Reply Quote
2/11/2014 08:16
I'm also getting incorrect resolutions off of opendns and google dns, so it's not just something odd with my local ISP.
Reply Quote
2/10/2014 07:28
What do you mean by mismatched?

comgendre is resolving (but using the wrong ns# server)  However, diskclock.com is using an old ns522.pair.com again and no longer resolves.
Reply Quote
2/9/2014 17:53
comgendre.com is using mismatched name servers.  Is that intentional?

https://www.dynadot.com/domain/ip.html?domain=comgendre.com
Reply Quote
2/7/2014 18:32
Instant Reply Here
Reply Quote
2/7/2014 06:21
comgendre.com is still coming up as ns522.pair.com where it should be dns.pair.com.  Others have the wrong ns# server or have the servers in a different order than I entered, but comgendre is the only one that's not resolving at the moment.
Reply Quote
2/6/2014 16:06
We had no reported issues regarding propagation time.  Are you still experiencing these issue?
Reply Quote
2/4/2014 06:51
Okay... diskclock.com fixed itself, but now comgendre.com has the wrong DNS servers.  I checked this one yesterday and it was fine.
Reply Quote
2/3/2014 07:31
wondible.com seems to be behaving, but diskclock.com is still wrong.



Dynadot IP Lookup:

Registry Name Servers
dns.pair.com
ns7.ns0.com

Zone Name Servers
dns.pair.com
ns7.ns0.com


-----------------


dig diskclock.com

; <<>> DiG 9.8.3-P1 <<>> diskclock.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35514
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;diskclock.com.                 IN      A

;; ANSWER SECTION:
diskclock.com.          3600    IN      A       209.68.26.128

;; AUTHORITY SECTION:
diskclock.com.          3600    IN      NS      ns522.pair.com.
diskclock.com.          3600    IN      NS      ns7.ns0.com.

;; Query time: 35 msec
;; SERVER: 64.135.192.8#53(64.135.192.8)
;; WHEN: Mon Feb  3 09:18:02 2014
;; MSG SIZE  rcvd: 94
Reply Quote