2degrees DNS IPv4 DNS server issues?

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

spacedog

496 posts

Ultimate Geek
+1 received by user: 62

#303140 19-Jan-2023 11:43

Anyone having issues with 111.69.69.68 or 111.69.69.68 today?

I am getting Query refused and can't figure out what's up? I did have them rotate my static IP this morning to a new one, but no issues if I use an external dns like cloudflare or google?

@2degrees?

NickMack

977 posts

Ultimate Geek
+1 received by user: 831

Trusted

In memoriam

Lifetime subscriber

#3023673 19-Jan-2023 12:30

Hi Space,

All appear to be online (up) https://smokeping.thenet.gen.nz/smokeping/smokeping.cgi?target=Local, There was a change (i suspect a fault, that has increased the latency to the US based DNS server) as per the graph.

How are you testing queries and to where, and do you have examples of refused? It's possible if you've been allocated another static and all are refusing that you may have been allocated one that is already allocated, but the testing below might provide some insight

C:\nslookup -server www.trademe.co.nz 111.69.69.68
*** Invalid option: server
Server: resolver01.2degrees.nz
Address: 111.69.69.68

Non-authoritative answer:
Name: www.trademe.co.nz
Addresses: 151.101.130.137
151.101.194.137
151.101.66.137
151.101.2.137

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

spacedog

496 posts

Ultimate Geek
+1 received by user: 62

#3023867 19-Jan-2023 12:58

@NickMack been on hold with @2degrees support and they rotated my static again, but I still cannot make any queries to 111.69.69.68 or .69.

Some more information. I'm using an Asus RT-AX86U as my router and I don't have IPv6 enabled since I have a static IP and didn't see any need to use IPv6. I can't recall exactly the last time I ran some nslookup's and they worked, but it was probably back in December as I was away from home over the holiday break. It's not something I do everyday, but I do it pretty frequently.

I also suspect this might pre-date my request to change static IP's because earlier this week, I decided to change/update my DDNS hostname (I use no-ip) and I noticed it wasn't able to update. I investigated my router logs and saw the router was issuing this error:

May 5 17:08:03 inadyn[3182]: Failed resolving hostname dynupdate.no-ip.com: Temporary failure in name resolution

That's when decided to run some nslookup commands from my computer and I get the following

C:\Windows\System32>nslookup google.com
Server: UnKnown
Address: 111.69.69.68

*** UnKnown can't find google.com: Query refused

Furthermore, I can see that my router itself isn't updating it's system clock via NTP after rebooting the router. I also fired up my laptop and tested nslookup and it fails as well

C:\Windows\System32>nslookup -server google.com 111.69.69.69
*** Invalid option: server
Server: UnKnown
Address: 111.69.69.69

*** UnKnown can't find google.com: Query refused

However, using cloudflare, there's no issue:

C:\Windows\System32>nslookup -server google.com 1.1.1.1
*** Invalid option: server
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
Name: google.com
Addresses: 2404:6800:4006:810::200e
172.217.167.110

Finally, if I go into the Asus Router WAN configuration and tell it not to use the ISP assigned DNS and use Google or Cloudflare, then it instantly update the system clock and DDNS works.

As a final point, this could have been going on for a little while because I have my DHCP server configured to pass my clients 111.69.69.68 for DNS 1 and then 1.1.1.1 for DNS2. I now suspect I have been failing over to DNS 2 in my configurations for a little while which may have obfuscated this problem for awhile.

davidcole

6099 posts

Uber Geek
+1 received by user: 1465

Trusted

#3023868 19-Jan-2023 12:59

Having had to scrabble around for the 2degrees dns servers a while back, is there a reliable srouce I can bookmark for if I do need them? 99% of the time they are fine, but every so often I've had to enter them directly in my unifi controller to get somethign to resume (last case of course was my fault putting a weird new dhcp/dns server in the network). BUt my only resolution was to force some dns servers I found somewhere for 2degrees.

Previously known as psycik

Home Assistant: Gigabyte AMD A8 Brix, Home Assistant with Aeotech ZWave Controller, Raspberry PI, Wemos D1 Mini, Zwave, Shelly Humidity and Temperature sensors
Media:Chromecast v2, ATV4 4k, ATV4, HDHomeRun Dual
Server Host Plex Server 3x3TB, 4x4TB using MergerFS, Samsung 850 evo 512 GB SSD, Proxmox Server with 1xW10, 2xUbuntu 22.04 LTS, Backblaze Backups, usenetprime.com fastmail.com Sharesies Trakt.TV Sharesight

NickMack

977 posts

Ultimate Geek
+1 received by user: 831

Trusted

In memoriam

Lifetime subscriber

#3023872 19-Jan-2023 13:12

spacedog:

@NickMack been on hold with @2degrees support and they rotated my static again, but I still cannot make any queries to 111.69.69.68 or .69.

Some more information. I'm using an Asus RT-AX86U as my router and I don't have IPv6 enabled since I have a static IP and didn't see any need to use IPv6. I can't recall exactly the last time I ran some nslookup's and they worked, but it was probably back in December as I was away from home over the holiday break. It's not something I do everyday, but I do it pretty frequently.

I also suspect this might pre-date my request to change static IP's because earlier this week, I decided to change/update my DDNS hostname (I use no-ip) and I noticed it wasn't able to update. I investigated my router logs and saw the router was issuing this error:

May 5 17:08:03 inadyn[3182]: Failed resolving hostname dynupdate.no-ip.com: Temporary failure in name resolution

That's when decided to run some nslookup commands from my computer and I get the following

C:\Windows\System32>nslookup google.com
Server: UnKnown
Address: 111.69.69.68

*** UnKnown can't find google.com: Query refused

Furthermore, I can see that my router itself isn't updating it's system clock via NTP after rebooting the router. I also fired up my laptop and tested nslookup and it fails as well

C:\Windows\System32>nslookup -server google.com 111.69.69.69
*** Invalid option: server
Server: UnKnown
Address: 111.69.69.69

*** UnKnown can't find google.com: Query refused

However, using cloudflare, there's no issue:

C:\Windows\System32>nslookup -server google.com 1.1.1.1
*** Invalid option: server
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
Name: google.com
Addresses: 2404:6800:4006:810::200e
172.217.167.110

Finally, if I go into the Asus Router WAN configuration and tell it not to use the ISP assigned DNS and use Google or Cloudflare, then it instantly update the system clock and DDNS works.

As a final point, this could have been going on for a little while because I have my DHCP server configured to pass my clients 111.69.69.68 for DNS 1 and then 1.1.1.1 for DNS2. I now suspect I have been failing over to DNS 2 in my configurations for a little while which may have obfuscated this problem for awhile.

Hiya, Both work for me, seems like there maybe an issue with the IP allocated. Can you ping 202.37.101.1, www.trademe.co.nz ?

C:\>nslookup -server google.com 111.69.69.69
*** Invalid option: server
Server: resolver02.2degrees.nz
Address: 111.69.69.69

Non-authoritative answer:
Name: google.com
Addresses: 2404:6800:4006:812::200e
142.250.67.14

C:\>nslookup -server google.com 111.69.69.68
*** Invalid option: server
Server: resolver01.2degrees.nz
Address: 111.69.69.68

Non-authoritative answer:
Name: google.com
Addresses: 2404:6800:4006:812::200e
142.250.67.14

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

#3023876 19-Jan-2023 13:15

@aspired

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

spacedog

496 posts

Ultimate Geek
+1 received by user: 62

#3023885 19-Jan-2023 13:24

No problem pinging those addresses:

C:\Windows\System32>ping www.trademe.co.nz

Pinging www.trademe.co.nz [151.101.66.137] with 32 bytes of data:
Reply from 151.101.66.137: bytes=32 time=3ms TTL=57
Reply from 151.101.66.137: bytes=32 time=3ms TTL=57
Reply from 151.101.66.137: bytes=32 time=4ms TTL=57
Reply from 151.101.66.137: bytes=32 time=4ms TTL=57

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

C:\Windows\System32>ping 202.37.101.1

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=3ms TTL=62
Reply from 202.37.101.1: bytes=32 time=2ms TTL=62
Reply from 202.37.101.1: bytes=32 time=2ms TTL=62
Reply from 202.37.101.1: bytes=32 time=2ms TTL=62

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

edit: I have 1.1.1.1 set as my secondary DNS which is why I'm able to resolve trademe.co.nz. If I take that out of the router, then I can't resolve anything.

Lego

Shop now for Lego sets and other gifts (affiliate link).

spacedog

496 posts

Ultimate Geek
+1 received by user: 62

#3023912 19-Jan-2023 14:06

So this issue must pre-date my static IP change made today. I had opened up another thread as I was having issues with one of my VOIP providers where some inbound calls were coming through and others were not. As soon as I set my router to use cloudflare instead of 2D DNS servers, the VoIP issue went away. That issue has been present for at least 3 days and quite possibly longer.

spacedog

496 posts

Ultimate Geek
+1 received by user: 62

#3025176 21-Jan-2023 14:43

Still waiting for any news from @2degrees. Several days later and I continue to get query refused from .69 and .68 DNS. Thank god for public dns servers....

aspired

33 posts

Geek
+1 received by user: 46

ID Verified

Trusted

2degrees

#3025713 23-Jan-2023 11:24

spacedog:

Still waiting for any news from @2degrees. Several days later and I continue to get query refused from .69 and .68 DNS. Thank god for public dns servers....

Can you please PM me your username and Ill have a look at what's going on

spacedog

496 posts

Ultimate Geek
+1 received by user: 62

#3025738 23-Jan-2023 13:07

@aspired thanks - sent!

spacedog

496 posts

Ultimate Geek
+1 received by user: 62

#3025793 23-Jan-2023 15:19

Special thanks to @aspired who has helped resolve the issue. DNS queries are no longer getting refused on my connection.

Geekzone support

Support Geekzone with one-off or recurring donations Donate via PressPatron.

decibel

335 posts

Ultimate Geek
+1 received by user: 224

#3025871 23-Jan-2023 16:52

Did you have the same problem on 202.37.101.1 and 2 ?

spacedog

496 posts

Ultimate Geek
+1 received by user: 62

#3025908 23-Jan-2023 19:34

funny you should ask that....for the life of me, I couldn't remember/locate the other/older snap.net.nz DNS servers the other day as I wanted to test against them, but I totally forgot Steve Gibson's DNSBench would have picked that up (great tool, DNSBench).

By the time I ran DNSBench, @aspired had already resolved the issue so I can't say whether it was just those nameservers or not.