Unbound doesn´t resolve "deutsche-glasfaser.de"?

Help
1

Hi,

I installed unbound on my pi.

All runs great, but I recognize, that domain
deutsche-glasfaser.de
doesn´ resolve an ip?!

On ssh I tried:

dig deutsche-glasfaser.de @127.0.0.1 -p5335

; <<>> DiG 9.16.1-Ubuntu <<>> deutsche-glasfaser.de @127.0.0.1 -p5335
;; global options: +cmd
;; connection timed out; no servers could be reached

On Google-DNS it works great

dig deutsche-glasfaser.de @8.8.8.8

; <<>> DiG 9.16.1-Ubuntu <<>> deutsche-glasfaser.de @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40189
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;deutsche-glasfaser.de.         IN      A

;; ANSWER SECTION:
deutsche-glasfaser.de.  21600   IN      A       185.22.44.179

;; Query time: 36 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sun Mar 13 09:41:01 CET 2022
;; MSG SIZE  rcvd: 66

Other Domains on unbound works also great:

dig heise.de @127.0.0.1 -p5335

; <<>> DiG 9.16.1-Ubuntu <<>> heise.de @127.0.0.1 -p5335
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33145
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1472
;; QUESTION SECTION:
;heise.de.                      IN      A

;; ANSWER SECTION:
heise.de.               86400   IN      A       193.99.144.80

;; Query time: 40 msec
;; SERVER: 127.0.0.1#5335(127.0.0.1)
;; WHEN: Sun Mar 13 09:41:28 CET 2022
;; MSG SIZE  rcvd: 53

So, where is the Problem?

Greets

Byte

2

Works here.

3

Thanks, but this didnt help me much.

4

If the rest of your daily domains works I woul try to disable the blocklists step by step and find out if this specific deny is caused here.

dig deutsche-glasfaser.de @127.0.0.1 -p5335

; <<>> DiG 9.16.22-Raspbian <<>> deutsche-glasfaser.de @127.0.0.1 -p5335
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26587
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1472
;; QUESTION SECTION:
;deutsche-glasfaser.de. IN A

;; ANSWER SECTION:
deutsche-glasfaser.de. 81626 IN A 185.22.44.179

;; Query time: 0 msec
;; SERVER: 127.0.0.1#5335(127.0.0.1)
;; WHEN: Sun Mar 13 12:05:10 CET 2022
;; MSG SIZE rcvd: 66

5

Hi,

there is no blocklist! I´ve disabled pi-hole.

Greets

6

Although I think there will be no difference, there should be a space between -p and the port number.

This doesn't only resolve to an IP, but means unbound did not receive the query at all.
What OS are you using?

7

Since this DNS query was routed directly to unbound (and not via Pi-hole), no blocking from Pi-hole would be in effect.

8

You will need to look under the hood with unbound to see why this specific query has failed. In your unbound configuration file that you installed using the Pi-hole unbound guide, change the verbosity to 5. Restart unbound, repeat the query, then look at the details in the unbound log.

Don't forget to reduce the verbosity at the end of troubleshooting, or the unbound log will grow quite quickly.

1 Like
9

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