DNS Disruption message in router event log

Forums › Spark New Zealand (including Skinny and BigPipe) › DNS Disruption message in router event log

surfisup1000

5288 posts

Uber Geek
+1 received by user: 2159

#305802 4-Jun-2023 20:48

I'm getting this message several times a day in the fritzbox, it causes internet dropout when it occurs...

DNS disruption detected; name resolution will now take place via public DNS servers.

DNS disruption ended; name resolution via public DNS servers ended.

On skinny fibre unlimited, using default skinny dns settings. It's been occurring up to a month now.

Any ideas?

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#3084967 4-Jun-2023 23:02

Have you tried using a different DNS - Cloudflare for example (1.1.1.1 and 1.0.0.1)? If it doesn't show any errors then perhaps the Skinny DNS might be causing it?

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

surfisup1000

5288 posts

Uber Geek
+1 received by user: 2159

#3085033 5-Jun-2023 08:53

I'll give it a go for a while, thanks :)

cbrpilot

964 posts

Ultimate Geek
+1 received by user: 555

Trusted

Spark NZ

#3085594 6-Jun-2023 16:06

No known issues on the Spark DNS servers. I'm guessing your logs don't show which URL it was trying to look up when it got a failure?

My views are my own, and may not necessarily represent those of my employer.

surfisup1000

5288 posts

Uber Geek
+1 received by user: 2159

#3085650 6-Jun-2023 16:28

cbrpilot:

No known issues on the Spark DNS servers. I'm guessing your logs don't show which URL it was trying to look up when it got a failure?

I could perhaps manually set the DNS server. Then, I will know which one.

It's not a big deal, just something I recently noticed. It'll probably go away one day. The fritz automatically swaps over to public dns so it has limited impact .

If it becomes more annoying I'll look further into it.