1
24.1 Legacy Series / Re: DNS resolution failing using DHCP supplied DNS servers
« on: May 04, 2024, 11:25:19 am »
Slept on it and did some troubleshooting this morning. Finally established it was the FW rules I'd put in that was not allowing connectivity.
The rules:
DNS lookup was failing because in for the Interface section I'd used an inverse match for the WAN internface (!WAN), for some reason this was causing lookups to fail from the DNS server in vlan1 to the Internet. I removed the interface match and it all works as expected.
These are inbound rules on the router so I didn't think they would affect the lookups out to the WAN. Clearly I don't quite understand the inverse match logic, or the DNS traffic flow from my own local recursive resolver to the Internet.
Does this make sense? Can anyone help me understand how the inverse match on the WAN interface would affect lookups from my local server?
The rules:
DNS lookup was failing because in for the Interface section I'd used an inverse match for the WAN internface (!WAN), for some reason this was causing lookups to fail from the DNS server in vlan1 to the Internet. I removed the interface match and it all works as expected.
These are inbound rules on the router so I didn't think they would affect the lookups out to the WAN. Clearly I don't quite understand the inverse match logic, or the DNS traffic flow from my own local recursive resolver to the Internet.
Does this make sense? Can anyone help me understand how the inverse match on the WAN interface would affect lookups from my local server?