DNS issues?

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › DNS issues?

nate

6473 posts

Uber Geek

Retired Mod

Trusted

Lifetime subscriber

#208432 11-Feb-2017 18:35

My parents have a Snap login (ADSL2) and have been having issues loading particular images off Facebook, and some NZ Herald content.

Swapped out the modem, still no luck. Changed their computers to use Google DNS - all better.

DNS servers are 202.37.101.1 and 202.37.101.2 - anyone else seeing any issues? They reckon it's been happening since Wednesday.

Spyware

3767 posts

Uber Geek

Lifetime subscriber

#1718729 11-Feb-2017 18:46

PRTG has been sending me emails because of timeouts connecting to bender.snap.net.nz since Thursday night.

Spark Max Fibre using Mikrotik CCR1009-8G-1S-1S+, CRS125-24G-1S, Unifi UAP, U6-Pro, UAP-AC-M-Pro, Apple TV 4K (2022), Apple TV 4K (2017), iPad Air 1st gen, iPad Air 4th gen, iPhone 13, SkyNZ3151 (the white box). If it doesn't move then it's data cabled.

JeremyNzl

359 posts

Ultimate Geek

#1718782 11-Feb-2017 22:48

I've been getting Host not found (I think that was the error in chrome) , then 3 seconds later the page loads on some international sites.

On Snap/degrees vdsl2 using default resolvers maybe for the last 2 weeks on and off its not constant

Unwilling to use google as i believe i can notice the micro lag between the snap and google

Call me crazy

C:\Users\Mexican>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=53ms TTL=60
Reply from 8.8.8.8: bytes=32 time=54ms TTL=60
Reply from 8.8.8.8: bytes=32 time=52ms TTL=60
Reply from 8.8.8.8: bytes=32 time=52ms TTL=60

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 54ms, Average = 52ms

C:\Users\Mexican>ping 202.37.101.1

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=17ms TTL=61
Reply from 202.37.101.1: bytes=32 time=17ms TTL=61
Reply from 202.37.101.1: bytes=32 time=17ms TTL=61
Reply from 202.37.101.1: bytes=32 time=17ms TTL=61

Ping statistics for 202.37.101.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 17ms, Average = 17ms

nitrotech

1285 posts

Uber Geek

#1718783 11-Feb-2017 22:51

Yep, same on 2d gig fibre

nate

6473 posts

Uber Geek

Retired Mod

Trusted

Lifetime subscriber

#1718890 12-Feb-2017 13:43

Has 2degrees admitted there's an issue? any ETA on a resolution?

ANglEAUT

2329 posts

Uber Geek

Trusted

Lifetime subscriber

#1718898 12-Feb-2017 14:13

JeremyNzl: ... Unwilling to use google as i believe i can notice the micro lag between the snap and google ...

Then I guess OpenDNS (208.67.222.222 & 208.67.220.220 | 2620:0:ccc::2 & 2620:0:ccd::2) is also out of the question?

Please keep this GZ community vibrant by contributing in a constructive & respectful manner.

yitz

2083 posts

Uber Geek

#1718900 12-Feb-2017 14:16

Does anyone know if their server addresses 202.37.101.1 and 202.37.101.2 are anycasted?

JeremyNzl

359 posts

Ultimate Geek

#1718901 12-Feb-2017 14:18

IcI:

JeremyNzl: ... Unwilling to use google as i believe i can notice the micro lag between the snap and google ...

Then I guess OpenDNS (208.67.222.222 & 208.67.220.220 | 2620:0:ccc::2 & 2620:0:ccd::2) is also out of the question?

C:\Users\Jerem>ping 208.67.222.222

Pinging 208.67.222.222 with 32 bytes of data:
Reply from 208.67.222.222: bytes=32 time=60ms TTL=60
Reply from 208.67.222.222: bytes=32 time=57ms TTL=60
Reply from 208.67.222.222: bytes=32 time=66ms TTL=60
Reply from 208.67.222.222: bytes=32 time=57ms TTL=60

Ping statistics for 208.67.222.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 66ms, Average = 60ms

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

wazzageek

1093 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#1718904 12-Feb-2017 14:37

JeremyNzl:

Unwilling to use google as i believe i can notice the micro lag between the snap and google

Call me crazy

Can you use a local DNS resolver, sending the requests to your upstream providers? (This will only really help if sites are using sensible TTLs)

2degreesCare

1537 posts

Uber Geek

Trusted

2degrees

#1719303 13-Feb-2017 11:41

Hey All,

We've discovered a minor issue in the configuration that may have been causing this, which has been corrected this morning. This should resolve the behaviour you have reported, let us know if this continues and we'll continue checking it out.

yitz: Does anyone know if their server addresses 202.37.101.1 and 202.37.101.2 are anycasted?

Yes, they are, your queries will be sent to the nearest server on our network.

Thanks,

Ralph ^JOB