1
23.7 Legacy Series / Re: I Can't Forward to My Local DNS Server
« on: January 24, 2024, 05:50:33 pm »
IT WAS REBIND PROTECTION THE WHOLE TIME
ANSWER:
I just used UnboundDNS and went to services -> unbound -> advanced -> Rebind protection networks
I removed the entry where it says 192.168.0.0/16. This solved the issue and there is no need to muck with the firewall rules or anything like that.
I looked at the possible settings on DNSmasq and there is no configuration for rebind protection. And I know for a fact that it does enforce some protection since there was a log entry that mentioned
Warning dnsmasq possible DNS-rebind attack detected: my.domain
I think if you're really determined to solve it on DNSmasq, you can ssh and change the configuration files directly.
MY LIFE'S STORY:
I was trying for so long to get Unbound and DNSmasq to forward but they both were blocking answers to my local network. The main reason that I even had the local DNS server is to resolve my local services to my local servers. This makes everything much smoother for example, on my phone. But I think that the default is to block answers to local addresses so that no one intercepts the local DNS server and forwards to a man-in-the-middle. I think that it's a crazy idea unless you have a public network accessible to anyone. But on OPNSense, you have all of the control on the LAN and if someone somehow intercepts your DNS queries in the LAN, you're already toast. But that's just me. I hope this helps someone else.
ANSWER:
I just used UnboundDNS and went to services -> unbound -> advanced -> Rebind protection networks
I removed the entry where it says 192.168.0.0/16. This solved the issue and there is no need to muck with the firewall rules or anything like that.
I looked at the possible settings on DNSmasq and there is no configuration for rebind protection. And I know for a fact that it does enforce some protection since there was a log entry that mentioned
Warning dnsmasq possible DNS-rebind attack detected: my.domain
I think if you're really determined to solve it on DNSmasq, you can ssh and change the configuration files directly.
MY LIFE'S STORY:
I was trying for so long to get Unbound and DNSmasq to forward but they both were blocking answers to my local network. The main reason that I even had the local DNS server is to resolve my local services to my local servers. This makes everything much smoother for example, on my phone. But I think that the default is to block answers to local addresses so that no one intercepts the local DNS server and forwards to a man-in-the-middle. I think that it's a crazy idea unless you have a public network accessible to anyone. But on OPNSense, you have all of the control on the LAN and if someone somehow intercepts your DNS queries in the LAN, you're already toast. But that's just me. I hope this helps someone else.