Unable to ping local host names

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

I had to redo my pi-hole due to a failure on my sd card. Using Pi 3B with Buster

Expected Behaviour:

Should be able to ping local host names

Actual Behaviour:

ping: Pi-WX: No address associated with hostname

Debug Token:

https://tricorder.pi-hole.net/mlw0hhi97z

Did you intend for the local domain to be 503?

    CONDITIONAL_FORWARDING=true
    CONDITIONAL_FORWARDING_IP=192.168.1.1
    CONDITIONAL_FORWARDING_DOMAIN=503
    CONDITIONAL_FORWARDING_REVERSE=1.168.192.in-addr.arpa

What does a dig for the local host name show for results?

yes domain is correct.

pi@Pi-Hole:~ $ dig

; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>>
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58936
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;.                              IN      NS

;; ANSWER SECTION:
.                       59794   IN      NS      e.root-servers.net.
.                       59794   IN      NS      h.root-servers.net.
.                       59794   IN      NS      l.root-servers.net.
.                       59794   IN      NS      i.root-servers.net.
.                       59794   IN      NS      a.root-servers.net.
.                       59794   IN      NS      d.root-servers.net.
.                       59794   IN      NS      c.root-servers.net.
.                       59794   IN      NS      b.root-servers.net.
.                       59794   IN      NS      j.root-servers.net.
.                       59794   IN      NS      k.root-servers.net.
.                       59794   IN      NS      g.root-servers.net.
.                       59794   IN      NS      m.root-servers.net.
.                       59794   IN      NS      f.root-servers.net.

;; Query time: 15 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Feb 18 14:44:18 EST 2020
;; MSG SIZE  rcvd: 239
pi@Pi-Hole:~ $ dig localhost

; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> localhost
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9530
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
localhost.              2       IN      A       127.0.0.1

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Feb 18 14:44:51 EST 2020
;; MSG SIZE  rcvd: 54
pi@Pi-Hole:~ $ dig pi-hole

; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> pi-hole
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19517
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;pi-hole.                       IN      A

;; ANSWER SECTION:
pi-hole.                2       IN      A       127.0.1.1

;; Query time: 7 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Feb 18 14:45:10 EST 2020
;; MSG SIZE  rcvd: 52

dig the client name your trying to ping.

And also dig pi.hole @192.168.1.254 to check Pi-hole. Note the spelling of the domain name.

pi@Pi-Hole:~ $ dig Pi-WX

; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> Pi-WX
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48894
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;Pi-WX.                         IN      A

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Feb 18 14:54:16 EST 2020
;; MSG SIZE  rcvd: 34

pi@Pi-Hole:~ $ dig pi.hole @192.168.1.254

; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> pi.hole @192.168.1.254
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12150
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
pi.hole.                2       IN      A       192.168.1.254

;; Query time: 0 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Tue Feb 18 14:54:56 EST 2020
;; MSG SIZE  rcvd: 52

Try dig Pi-WX @192.168.1.254

pi@Pi-Hole:~ $ dig Pi-WX @192.168.1.254

; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> Pi-WX @192.168.1.254
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22229
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;Pi-WX.                         IN      A

;; Query time: 1 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Tue Feb 18 14:57:43 EST 2020
;; MSG SIZE  rcvd: 34

Okay, Pi-hole doesn't know the local name. How are you adding the names to Pi-hole?

I am not should it not be dynamic?

If you're not manually entering the name and not using Pi-hole as the DHCP server then there's no way for Pi-hole to know about the names.

I knew i forgot one step was :slight_smile:

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