strange unbound issue

[JohnDow]

not resolve web.whatsapp.com

but all other work and resolve.
mystics, please help with diagnostics.

Spoiler

||

[Gertjan]

@JohnDow said in strange unbound issue:

web.whatsapp.com

Not hard :

so no one "picks up the phone" at 127.0.0.1 port 53. This means : unbound isn't running (or brain dead).

Let start with the basics :
What is your pfSense version ?
Running bare bone, VM, other ?
What were the other DNS settings you've changed ?
Go to Services >DNS Resolver > General Settings and at the bottom (nearly) of the page hit Save - and then Apply at the top of the page. Now go to the page with the answers : Status > System Logs > System > DNS Resolver : what happened ?

[JohnDow]

This post is deleted!

[JohnDow]

@Gertjan said in strange unbound issue:

his means : unbound isn't running (or brain dead).
it work in all other sites

but **all other work and resolve**.

in second pics resolve google

Version 2.7.1-RELEASE (amd64)
built on Wed Nov 29 23:08:00
FreeBSD 14.0-CURRENT
work on non brand old (2lans) comp
until update 2.7.1 unbound work perfectly.
0 ms but not resolve only web.whatsapp.com

Spoiler

[Gertjan]

@JohnDow said in strange unbound issue:

0 ms but not resolve only web.whatsapp.com

For whatever reason, your "Results" part is missing.

unbound, this time, replied within "0 ms", the others within 17 ms.
But no answer - for you. I did have an answer.
That for you, 8.8.8.8 hasn't an answer neither .... that's puzzling.

If I ask "8.8.8.8" manually :

[23.09-RELEASE][root@pfSense.bhf.tld]/root: dig @8.8.8.8 web.whatsapp.com +short
mmx-ds.cdn.whatsapp.net.
31.13.83.51

Try this one for yourself.

Can you also show a :

dig web.whatsapp.com

?

[JohnDow]

This post is deleted!

[JohnDow]

@Gertjan said in strange unbound issue:

dig web.whatsapp.com

Shell Output - dig web.whatsapp.com

;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: timed out

; <<>> DiG 9.18.19 <<>> web.whatsapp.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1471
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
web.whatsapp.com. 37 IN CNAME mmx-ds.cdn.whatsapp.net.
mmx-ds.cdn.whatsapp.net. 38 IN A 157.240.0.60

;; Query time: 18 msec
;; SERVER: 77.88.8.8#53(77.88.8.8) (UDP)
;; WHEN: Wed Dec 06 16:57:20 MSK 2023
;; MSG SIZE rcvd: 98

Shell Output - dig @8.8.8.8 web.whatsapp.com +short

mmx-ds.cdn.whatsapp.net.
157.240.205.60

[SteveITS]

@JohnDow said in strange unbound issue:

;; communications error to 127.0.0.1#53: timed out

So as noted is unbound (DNS Resolver) running? Check Status/DNS Resolver and the icons at the top bar.

In System/General Setup to what is "DNS Resolution Behavior" set?

[Gertjan]

@JohnDow

Can you open up a console, or better, a SSH session, use option 8 ( Shell ) and use this command :

tail -f /var/log/resolver.log

and tell, show us, what you saw ?