DNS server not responding to external requests

BIND 9.20.29 (Stable Release)
Firewall/router Sonicwall tz350

From a remote host I issue the following request:

$ host sma-inc.us ns1.sma-inc.us
;; communications error to 192.88.109.73#53: timed out
;; communications error to 192.88.109.73#53: timed out
;; no servers could be reached

Hmm. Not good.
The log of the target (local) DNS server has these entries, which seem to indicate the server responded. Yet the remote host claims a timeout, as above.

13-Oct-2026 14:34:45.532 queries: info: client @0x7fcc5192a800 35.212.19.78#36115 (sma-inc.us): query: sma-inc.us IN A + (192.168.69.109)
13-Oct-2026 14:34:45.532 responses: info: client @0x7fcc5192a800 35.212.19.78#36115 (sma-inc.us): response: sma-inc.us IN A NOERROR 1 0 0 + (192.168.69.109)
13-Oct-2026 14:34:50.537 queries: info: client @0x7fcc4dcaac00 35.212.19.78#51412 (sma-inc.us): query: sma-inc.us IN A + (192.168.69.109)
13-Oct-2026 14:34:50.537 responses: info: client @0x7fcc4dcaac00 35.212.19.78#51412 (sma-inc.us): response: sma-inc.us IN A NOERROR 1 0 0 + (192.168.69.109)

Note: 35.212.19.78 is the IP for sohnen-moe.com.

What would prevent the outgoing response?

First suspicion - Behind a firewall?

You could examine with tcpdump. Capture packets on the DNS server while repeating the remote query…

sudo tcpdump -ni any 'host 35.212.19.78 and port 53'

Look for the incoming query and outgoing response. If the response is occurring as expected, then investigate routing or NAT. Otherwise check the firewall.

Hmm. Looks good at the local server host:

$ tcpdump -v -ni any 'host 35.212.19.78 and port 53'
tcpdump: WARNING: any: That device doesn't support promiscuous mode
(Promiscuous mode not supported on the "any" device)
tcpdump: listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
14:59:37.879452 eth0  In  IP (tos 0x60, ttl 115, id 54398, offset 0, flags [none], proto UDP (17), length 56)
    35.212.19.78.18808 > 192.168.69.109.53: 33691+ A? sma-inc.us. (28)
14:59:37.881854 eth0  Out IP (tos 0x0, ttl 64, id 7798, offset 0, flags [none], proto UDP (17), length 72)
    192.168.69.109.53 > 35.212.19.78.18808: 33691* 1/0/0 sma-inc.us. A 192.88.109.73 (44)
14:59:42.879543 eth0  In  IP (tos 0x0, ttl 114, id 4318, offset 0, flags [none], proto UDP (17), length 56)
    35.212.19.78.59075 > 192.168.69.109.53: 33691+ A? sma-inc.us. (28)
14:59:42.881421 eth0  Out IP (tos 0x0, ttl 64, id 12295, offset 0, flags [none], proto UDP (17), length 72)
    192.168.69.109.53 > 35.212.19.78.59075: 33691* 1/0/0 sma-inc.us. A 192.88.109.73 (44)

The next step is to look at the SonicWall then. Check if the response is forwarded out its WAN interface and whether NAT is applied correctly. Is it leaving the WAN interface?

As an experiment would you try the following command?
host sma-inc.us ns1.sma-inc.us

I have failed to get any kind of useful connection log from the firewall.

I have access to only one external host and it may be interfering with the transaction.
Well, that’s a (wild) conjecture, do not know why the ISP would do that; grasping at straws.

~> host sma-inc.us ns1.sma-inc.us
;; communications error to 192.88.109.73#53: timed out
;; communications error to 192.88.109.73#53: timed out
;; no servers could be reached

So much for that weird idea.
I finally got the connection log to show the DNS transaction. The log shows packets are received, and none are sent.

I thought maybe the NAT rule needed a complement to respond to the incoming DNS request. No luck there.

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