2Degrees / Snap DNS servers slow to pickup DNS changes?

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › 2Degrees / Snap DNS servers slow to pickup DNS changes?

1 | 2

CutCutCut

1039 posts

Uber Geek
+1 received by user: 53

#2605940 18-Nov-2020 12:26

NickMack:

CutCutCut:

Some of this is beyond my understanding, but I have a fixed IP and in the last week or so I've had a couple of weird things, like setting up a new ipad, i got a warning that the ipad I was trying to transfer to was located in Chrsitchurch, when I am near Auckland, and then yesterday, loggin into a microsft account and getting a warning of suspicious log in from Sydney, but then when I checked, it said it was in Chrsitchurch. And now I'm having trouble connecting to my Plex server remotely. Related?

Nope/unlikley - There are many databases across the globe that think they know where specific IP addresses are geographically located. ISPs move IP addresses around based on growth/needs and therefore keeping this information up to date in all databases is problematic. The issue we are talking about was DNS changes being slow to be picked up, using the right (new) DNS servers at 2degrees and then a discussion about latency to the new DNS servers compared to the old.

Nick.

Ahhh right, thanks!

spacedog

496 posts

Ultimate Geek
+1 received by user: 62

#2606432 18-Nov-2020 17:15

spacedog:

Looks like my router was not picking up the new DNS servers, but after refreshing the settings it's now pulling down

111.69.69.68
111.69.69.69

Those servers are showing the DNS change propagations that I made yesterday which is great. I would note that ns1.snap.net.nz is still not picking up any of the DNS changes I have made so there is some misalignment lag happening on the older servers. Not sure how much of a concern that is, but they do look pretty stale.

Just a follow-up...

ns1.snap.net.nz eventually picked up the changes but it took somewhere in the neighborhood of 30+ hours to pick it up. I know the default rule of thumb is to allow 24-48 hours for DNS propagation, but clearly the new resolver was getting the change *much* faster. And the reality is that these days I see most major DNS changes propagate in 1-4 hours (sometimes within 30 minutes).

NickMack

977 posts

Ultimate Geek
+1 received by user: 831

Trusted

In memoriam

Lifetime subscriber

#2610933 26-Nov-2020 09:04

Hi All,

Looks like changes were made in routing for the new DNS's resolvers (resolver01/02) which is excellent, thank you. @pwmer @morganbrowne

There's still an issue with latency to the CGNAT nodes however. e.g.: seeing ~17ms from CHC to CHC.

https://smokeping.thenet.gen.nz/smokeping/smokeping.cgi?target=2da10

Nick.

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

pwner

423 posts

Ultimate Geek
+1 received by user: 96

Trusted

2degrees

#2610962 26-Nov-2020 09:53

Hi Nick

Can you let me know what IPs you are using for the CGNAT reference points as they should be coming back with the same latency as the resolver addresses.

Any posts are personal comments and not that of my employer

NickMack

977 posts

Ultimate Geek
+1 received by user: 831

Trusted

In memoriam

Lifetime subscriber

#2610963 26-Nov-2020 09:55

pwner:

Hi Nick

Can you let me know what IPs you are using for the CGNAT reference points as they should be coming back with the same latency as the resolver addresses.

For sure, I'll PM you.

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

NickMack

977 posts

Ultimate Geek
+1 received by user: 831

Trusted

In memoriam

Lifetime subscriber

#2614625 2-Dec-2020 11:05

NickMack:

pwner:

Hi Nick

Can you let me know what IPs you are using for the CGNAT reference points as they should be coming back with the same latency as the resolver addresses.

For sure, I'll PM you.

Hi @pwner,

Any updates on CGNAT node latency?

Nick.

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

1 | 2