I just did a quick test:- portforwarding TCP 80 to internal Webserver- enable only "Reflection for port forwards"- create an A-record in Unbound with my external WAN IPWorks as expected
I am having the same issue, NAT reflection not working. I ended up making an override entry in Unbound for my internal webserver, but it only works if the client machine uses my internal dns server, which is handed out via DHCP, but anyone who sets it manually, the website resolves as my external IP, and doesn't NAT to the internal IP of the webserver.Seems to me this should be as simple as enabling "NAT reflection" in the port forward rule. Is this a bug or are we missing something? Using version 20.7.
Why? This is the same exact issue as @BeanAnimal and others, it's usually good forum etiquette to search for related topics instead of everyone creating a separate thread for the same problem...?I just resolved it though, I don't know if this is the "proper" way, but go to Firewall -> Settings -> Advancedand check "Reflection for port forwards", and for good measure "Reflection for 1:1", and "Automatic outbound NAT for Reflection".Hopefully this helps someone else, and I hope I haven't just created some nasty loops but so far so good.