Intermittent DNS Issues

Please follow the below template, it will help us to help you!

Expected Behaviour:

DNS Resolving

Actual Behaviour:

Sometimes my DNS isn’t resolving anything, if I reload a page it works again. I’ve been testing a bit using sudo pihole with differing results

Example:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] ad.doubleclick.net.50285.9279.302br.net is 0.0.0.0 via localhost (127.0.0.1)
[✓] ad.doubleclick.net.50285.9279.302br.net is 0.0.0.0 via Pi-hole (10.0.10.53)
[✓] doubleclick.com is 172.217.14.238 via a remote, public DNS server (8.8.8.8)

No changes, run again

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve concinnousaepwnh.download via localhost (127.0.0.1)
[✓] concinnousaepwnh.download is 0.0.0.0 via Pi-hole (10.0.10.53)
[✓] doubleclick.com is 172.217.14.238 via a remote, public DNS server (8.8.8.8)

Debug Token:

https://tricorder.pi-hole.net/6sx8dl96a4
and
https://tricorder.pi-hole.net/20nexds7tz

What is the difference between the two debug logs? First one when Pi-Hole is working properly, second when it is not?

That’s correct.

I don’t understand what you were doing with sudo pihole. Without command line arguments, that command shows the manual for the pihole command.

Can you walk us through the steps you were doing prior to the problem?

Sorry, I meant
sudo pihole -d

I’ve also been running nslookups from my windows PC and getting timeouts. With web browsing i’ll get the can’t find IP errors, hit reload and it comes right up.

Common now in nslookup
Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: google.ca
Address: 172.217.14.227

Don’t know if this helps narrow it down

dig google.com @127.0.0.1

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> google.com @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 30680
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com. IN A

;; Query time: 3233 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Jan 13 15:41:45 PST 2020
;; MSG SIZE rcvd: 39

and a few seconds later

dig google.com @127.0.0.1

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> google.com @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1439
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com. IN A

;; ANSWER SECTION:
google.com. 193 IN A 172.217.14.238

;; Query time: 1921 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Jan 13 15:44:27 PST 2020
;; MSG SIZE rcvd: 55

Trying to run the update check now

[✓] Detected x86_64 architecture
[i] Checking for existing FTL binary…
[i] Latest FTL Binary already installed (v4.3.1). Confirming Checksum…
curl: (6) Could not resolve host: github-production-release-asset-2e65be.s3.amazonaws.com
[i] Corruption detected…
[i] Downloading and Installing FTL…curl: (6) Could not resolve host: github-production-release-asset-2e65be.s3.amazonaws.com
[✗] Downloading and Installing FTL
Error: URL https://github.com/pi-hole/FTL/releases/download/v4.3.1/pihole-FTL-linux-x86_64 not found
[✗] FTL Engine not installed

Unable to complete update, please contact Pi-hole Support

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.