2Degrees DNS struggling / slow today?

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › 2Degrees DNS struggling / slow today?

spacedog

482 posts

Ultimate Geek

#310626 7-Nov-2023 14:03

Not sure what is going on with 2D DNS today. I was visiting a site yesterday and ordering some parts - www.theboltholder.co.nz - and it worked just fine.

Today I tried to go back and the site has been showing as unresolvable for several hours. If I directly query 111.69.69.69 or .68 it can't resolve. If I directly query Google DNS on 8.8.8.8 or Cloudflare on 1.1.1.1, no problems?

> server 1.1.1.1
Default Server: one.one.one.one
Address: 1.1.1.1

> www.theboltholder.co.nz
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
Name: www.theboltholder.co.nz
Address: 103.238.86.143

> server 111.69.69.69
Default Server: resolver02.2degrees.nz
Address: 111.69.69.69

> www.theboltholder.co.nz
Server: resolver02.2degrees.nz
Address: 111.69.69.69

*** resolver02.2degrees.nz can't find www.theboltholder.co.nz: Server failed
>

What gives?

NickMack

962 posts

Ultimate Geek

Trusted

Lifetime subscriber

#3156966 7-Nov-2023 14:07

I'm seeing timeouts too.

> server 111.69.69.69
DNS request timed out.
timeout was 2 seconds.
Default Server: [111.69.69.69]
Address: 111.69.69.69

> server 111.69.69.69
Default Server: resolver02.2degrees.nz
Address: 111.69.69.69

@aspired - it might need a reboot :-)

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

xpd

Geek @ Coastguard NZ
13766 posts

Uber Geek

Retired Mod

ID Verified

Trusted

Lifetime subscriber

#3156967 7-Nov-2023 14:15

Not working here either, and Im not on 2D.

Gavin / xpd / FastRaccoon / Geek of Coastguard New Zealand

LinkTree

spacedog

482 posts

Ultimate Geek

#3156968 7-Nov-2023 14:21

NickMack:

I'm seeing timeouts too.

> server 111.69.69.69
DNS request timed out.
timeout was 2 seconds.
Default Server: [111.69.69.69]
Address: 111.69.69.69

> server 111.69.69.69
Default Server: resolver02.2degrees.nz
Address: 111.69.69.69

@aspired - it might need a reboot :-)

@NickMack - you doing that from Windows using nslookup? I actually don't see a timeout error when I change the server using windows and nslookup? And other DNS queries seem fine, it's just that site?

aspired

32 posts

Geek

ID Verified

Trusted

2degrees

#3156969 7-Nov-2023 14:21

$ dig @ns1.dns.net.nz theboltholder.co.nz +noall +auth

theboltholder.co.nz. 86400 IN NS zelda.ns.cloudflare.com.

theboltholder.co.nz. 86400 IN NS ns1.discountdomains.co.nz.

theboltholder.co.nz. 86400 IN NS ns2.discountdomains.co.nz.

theboltholder.co.nz. 86400 IN NS major.ns.cloudflare.com.

theboltholder.co.nz. 86400 IN NS ns3.discountdomains.co.nz.

There are multiple nameservers for that domain and the Cloudflare ones are not responding to queries

NickMack

962 posts

Ultimate Geek

Trusted

Lifetime subscriber

#3156970 7-Nov-2023 14:24

aspired: $ dig @ns1.dns.net.nz theboltholder.co.nz +noall +auth theboltholder.co.nz. 86400 IN NS zelda.ns.cloudflare.com. theboltholder.co.nz. 86400 IN NS ns1.discountdomains.co.nz. theboltholder.co.nz. 86400 IN NS ns2.discountdomains.co.nz. theboltholder.co.nz. 86400 IN NS major.ns.cloudflare.com. theboltholder.co.nz. 86400 IN NS ns3.discountdomains.co.nz.
There are multiple nameservers for that domain and the Cloudflare ones are not responding to queries

From my side

nick@thenet-rs04:~$ dig @ns1.dns.net.nz theboltholder.co.nz +noall +auth

; <<>> DiG 9.11.3-1ubuntu1.19+esm2-Ubuntu <<>> @ns1.dns.net.nz theboltholder.co.nz +noall +auth
; (2 servers found)
;; global options: +cmd
theboltholder.co.nz. 86400 IN NS zelda.ns.cloudflare.com.
theboltholder.co.nz. 86400 IN NS major.ns.cloudflare.com.
theboltholder.co.nz. 86400 IN NS ns3.discountdomains.co.nz.
theboltholder.co.nz. 86400 IN NS ns1.discountdomains.co.nz.
theboltholder.co.nz. 86400 IN NS ns2.discountdomains.co.nz.

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

spacedog

482 posts

Ultimate Geek

#3157040 7-Nov-2023 15:48

Ok, sorry for the false alarm, guess they just have a buggy domain. Had issues with 2D DNS a few times in the past and thought this might be a 2D problem - sorry for casting false aspersions @aspired!

Just for my own knowledge and curiosity, does this suggest a problem with cloudflare, their cloudflare configuration, or have they just misconfigured misconfigured their domain in general?