Firewalla inconsistent DNS for local names... how to diagnose?
I have an FW:Purple in Router mode.
Hosts on my Main LAN resolve DNS queries for internet hosts like www.reddit.com just fine. However, they can't seem to reliably resolve DNS names for their peers on the same network.
My home network's DNS domain and search domain are set to blood (long story).
For example, the Windows box I'm on:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : blood
Link-local IPv6 Address . . . . . : <REDACTED>
IPv4 Address. . . . . . . . . . . : 192.168.109.156
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.109.1
Another machine on my network shows this in the Device Details:
| Device Name | N40 |
|---|---|
| Local Domain | n40.blood |
| IP Address | 192.168.109.89 |
...but for some reason none of my windows machines can resolve n40 or n40.blood (or other such boxes). Windows swears it's talking to the same nameserver:
A name not found error was returned for the name n40.blood. Check to ensure that the name is correct. The response was sent by the server at 192.168.109.1:53. Client PID 25996. Send Blob 0x1fc568b8f00. Context 0x7ffa545312e0
...but an ubuntu machine gives a different result:
> n40
Server: 192.168.109.1
Address: 192.168.109.1#53
Name: n40.blood
Address: 192.168.109.93
Name: n40.blood
Address: 192.168.109.89
Name: n40.blood
Address: ::
I thought this was a Windows problem, but one of my other Ubuntu machines has it too:
> n40.blood
Server: 192.168.109.1
Address: 192.168.109.1#53
** server can't find n40.blood: NXDOMAIN
It's just DNS AFAICT. All the machines can reach each other by IP.
Is there a way to turn on debugging or verbosity on the firewalla nameserver?
Thanks!