NAT on port 53

Started by ledaje, May 08, 2021, 09:51:37 PM

Previous topic - Next topic
OPNsense seems to take over port 53 when trying to NAT the port to an internal server?

I've tried to disable Unbound but that doesn't make NAT work. Do I need to do change a setting or make a configuration somewhere to make NAT work for port 53? (all other ports seem to work fine)

Thanks.



Try to tick
"Don't use local system as DNS server" or so under System->Settings->general
(Unoffial Community) OPNsense Telegram Group: https://t.me/joinchat/0o9JuLUXRFpiNmJk

PM for paid support

Quote from: lfirewall1243 on May 08, 2021, 10:16:26 PM
Try to tick
"Don't use local system as DNS server" or so under System->Settings->general

Thanks for the tip, but it wasn't what solved my issue. I had a NAT rule that was configured with "WAN address" as Destination and I thought WAN address meant the ONE IP that is configured as a primary IP on the WAN interface. But apparently, WAN address means all Virtual IPs which is configured on the WAN interface. Maybe "WAN address" should be called "All WAN addresses" instead if this is not a bug.

Have you disabled / port remapped your unbound / dnsmasq / bind DNS server usually running on Opnsense?