NZ DNS records not updating correctly with international change.

Forums › New Zealand Broadband › NZ DNS records not updating correctly with international change.

kinsten

240 posts

Master Geek

#136203 18-Nov-2013 19:15

Last Monday I updated my Name Servers IP address for my hosting account.
Amazingly it does not appear to be working within NZ with the new IP address. The only thing I can fathom is that because the original server is still functioning, it does not appear to be a priority.

Does anyone know how the NZ ISP's deal with DNS information udpates (setup via GoDaddy.com)?
We are talking ns1 & ns2 name server setups, each with a different IP address.
The domain itself points to , well itself (as per recommended setup).

A little concerned as the old server gets switched off this week.
And all emails and website services will most likely go down for a few hours/days while the ISP's actually attempt to update their records. Or stay broken until I contact them.

So far have checked 4 different ISP's all with the same results. The old IP address is being returned.

Thanks...

Intel Core 2 Duo E6600, 4x 2GB Adata 1066+ DDR2, Sapphire HD4850 X2 2GB GDDR3 PCI-E Quad DVI, 1000w PSU & over 4TB HDD space, Windows 7 Ultimate 64bit
PS3 Slim

mattwnz

20178 posts

Uber Geek

#936881 18-Nov-2013 19:40

Contact your host to see what they say. Did you just update the IPs and not the nameserver address on teh domain? You don't need to enter any IPs, just the nameservers for the domain.

Ragnor

8223 posts

Uber Geek

Trusted

#936882 18-Nov-2013 19:41

What should happen if you change nameservers is your registrar (presuming this is godaddy) updates the NZ SRS (assuming this is a .nz domain, otherwise it updates the appropriate regional registry) with a new record listing what nameservers should be used as authoritative for your domain. This should be pretty quick.. shouldn't take longer than 60min really.

However the actual DNS records (eg: what www.somedomain.co.nz resovles too) could still be cached in DNS servers around the world from before the change though if you had long TTL times set for those records.

Do you know what the TTL's were before the change?

DNS servers cache records using the TTL as a guide for how long they should keep the record before rechecking.

You don't want long TTL's if you are going to change things, otherwise the change won't be picked up for ages. Normally you'd lower the TTL's a few days before making changes.

Maybe the TTL was set to 24hrs or 48hrs or something?

There are a few good sites for checking "dns propagation", eg:
https://www.whatsmydns.net/
http://viewdns.info/propagation/
http://checkdnspropagation.com/

If you don't mind posting or private messaging the domain name, can easily do a few checks on it to see what's up.

kinsten

240 posts

Master Geek

#936974 18-Nov-2013 21:07

lol, well the name servers are mine...
this is the issue at hand, and there are a few dozen domains pointing to my name servers.

I actually enquired with GoDaddy (who host the domain which I use for the ns1 & ns2 nameservers), and they told me the only 2 places they could see which have not updated were Malaysia & China (which I am not concerned about). They did not however specifically say that there was a successful update from a NZ based server. Then of course asked me to clear all browsing history (which I have done and know is not the problem anyway).

I was using this website to do the test (which also does not include NZ).
http://cloudmonitor.ca.com/en/ping.php

For me the only places failing to return the new IP address are:
- Kuala Lumpur, Malaysia (mykul01)
- Ashburn, U.S.A. (usabn06)
Moscow and Russia servers do not appear to always return results.
I have noticed these results also seem to fluctuate depending on where I run the test from (work, home, other peoples home pc's). But generally are moving in the right direction.

Earlier today Sydney Australia also was not returning the correct IP address, but appears to be correct now.
It also became apparent whilst using several different pining websites, they only returned what standard command prompt ping would return, that in itself was a little frustrating for a while.

Tried talking with Telecom about this, but ended up in the Philippine's, they obviously had no idea what I was talking about, and also not being in the same country as us, could not provide me with with any real technical assistance at all.

Telstra (after 40 minutes on hold) then checked with their technical team (another 15 minutes on hold) and finally said they would forward the query to their main technical staff to address the issue.

I also have a friend from Gen-i checking something for me tomorrow with their techies.

So thinking if I am lucky, the problem should be sorted by tomorrow evening, wednesday morning..... =D
*fingers crossed*

But still, should a DNS resolution like this take over a week to update. I thought NZ was pretty good with this sort of thing.

Intel Core 2 Duo E6600, 4x 2GB Adata 1066+ DDR2, Sapphire HD4850 X2 2GB GDDR3 PCI-E Quad DVI, 1000w PSU & over 4TB HDD space, Windows 7 Ultimate 64bit
PS3 Slim

RunningMan

8964 posts

Uber Geek

#936979 18-Nov-2013 21:17

kinsten: [snip]
But still, should a DNS resolution like this take over a week to update. I thought NZ was pretty good with this sort of thing.

Quite possibly, yes. It will depend on the TTL that was set prior to the changes being made.

LennonNZ

2459 posts

Uber Geek

ID Verified

Trusted

#936983 18-Nov-2013 21:27

What is the Domain name and maybe we can tell you where the problem (if there is one) is occurring....

Ragnor

8223 posts

Uber Geek

Trusted

#937422 19-Nov-2013 16:42

RunningMan:
kinsten: [snip]
But still, should a DNS resolution like this take over a week to update. I thought NZ was pretty good with this sort of thing.

Quite possibly, yes. It will depend on the TTL that was set prior to the changes being made.

Exactly if you had your TTL set to something like 48hrs, then it will take upto 48hrs for some DNS servers to drop their cached records and recheck.

Working as intended.

kinsten

240 posts

Master Geek

#937897 20-Nov-2013 13:40

After speaking with the hosting company, they have assured me there should be no issues with DNS resolving old IP addresses, as they will redirect those internally from their end.

But they were also surprised after 8 days the DNS IP records were not updating accordingly.
Think I am going to move my name server and other domains away from GoDaddy anyway.

Thanks for everyones responses, the TTL thing totally did not even cross my mind when I went to change the IP addresses.

Intel Core 2 Duo E6600, 4x 2GB Adata 1066+ DDR2, Sapphire HD4850 X2 2GB GDDR3 PCI-E Quad DVI, 1000w PSU & over 4TB HDD space, Windows 7 Ultimate 64bit
PS3 Slim

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

Ragnor

8223 posts

Uber Geek

Trusted

#938063 20-Nov-2013 18:07

I got your PM and the SOA record doesn't look right to me, see my reply pm.