$ 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)
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.
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