ANSWERED DNS stops working

[Psamathe 2]

Also: 14 Jan 2022 12:50-13:00 (uncertain on exact time
(Following failure, switched VPN off, reverting to ISP's DNS and it immediately worked, switched VPN back on and it continued to work (IP address now cached?, reconnect reconnected to same AirVPN server)
 

• the fully qualified domain name you could not resolve: wildaboutthebritishisles.uk
• the server you were connected to: chow
• the connection mode and protocol (some OpenVPN mode or WireGuard): OpenVPN
• the DNS block lists you had active, if any: No lists a few custom domains
• the complete output of the command dig or nslookup pertaining to the "problematic" domain name:

  ; <<>> DiG 9.10.6 <<>> wildaboutthebritishisles.uk

  ;; global options: +cmd

  ;; Got answer:

  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 59754

  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

   

  ;; OPT PSEUDOSECTION:

  ; EDNS: version: 0, flags:; udp: 4096

  ;; QUESTION SECTION:

  ;wildaboutthebritishisles.uk. IN A

   

  ;; Query time: 3767 msec

  ;; SERVER: 10.14.80.1#53(10.14.80.1)

  ;; WHEN: Fri Jan 14 12:57:40 GMT 2022

  ;; MSG SIZE  rcvd: 56
  
   

Edited ... by Psamathe
Additional info

[OpenSourcerer 1435]

4 hours ago, Psamathe said:

;; Query time: 3951 msec

4 hours ago, Psamathe said:

;; Query time: 6437 msec

4 hours ago, Psamathe said:

;; Query time: 2072 msec 

4 hours ago, Psamathe said:

;; Query time: 930 msec

Those query times are absolutely insane.

Hey, if you do a +trace for any of those domains, does the resolution of the intermediate names take as long as this? Like so:

$ dig a in cycle.travel +trace

.

[Psamathe 2]

11 minutes ago, OpenSourcerer said:

Those query times are absolutely insane.

Hey, if you do a +trace for any of those domains, does the resolution of the intermediate names take as long as this? Like so:

$ dig a in cycle.travel +trace

I'll try next time.
When connected to VPN and the issue happens I generally browse to a web site I use a lot before anything else and that invariably responds quickly and immediately; domain name almost certainly previously resolved and cached as I try on a site I use all the time (e.g. UK MetOffice). Moment I switch to ISP (disconnect from VPN) it immediately works (i.e. onto ISP's DNS.

[Flx 76]

Use your router IP and serve DNS over the connected server on your flashed router. Internal DNS vs. External/Global DNS.
Reference(Internal root DNS and other facts):
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/ee649129(v=ws.10)

[Psamathe 2]

8 hours ago, Flx said:

Use your router IP and serve DNS over the connected server on your flashed router. Internal DNS vs. External/Global DNS.
Reference(Internal root DNS and other facts):
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/ee649129(v=ws.10)

Afraid that means nothing to me. I don't have a flashed router, I use a Mac, I don't have a lot of what that document is talking about. In English? None of the linked document seems to apply so I'm lost.

[Flx 76]

12 hours ago, Psamathe said:

None of the linked document seems to apply so I'm lost.

That was not for you. Advise and Referenced link was for Mr. @root1337 @Karmatron 

[Staff 9972]

Hello everybody,

can you please re-perform all of your tests and report back? We have found a bug which potentially might have caused the reported names resolution failures under rare circumstances on a few servers. We have fixed the code. Please let us know whether the problems keeps occurring or not, as our automated DNS testing sentinels deployed on the reported flag servers have stopped reporting resolution failures since when the fix was deployed. A couple of hours ago the fix has been deployed.


Kind regards
 

Edited ... by Staff
Typo

[Staff 9972]

Hello!

Since no reports came in here or in tickets in the last 10 days we consider the problem as resolved, thank you very much!

Kind regards