Need to convene the brain trust on DNS rebinding issue

sensewolf

Anyone who has had this issue and resolved it successfully?

I have come across so many instances in other forums where this has become a problem with one service or another - there has to be a solution...

Unfortunately, designating the domain private in the DNS resolver has not helped. From what I understand it should, but it doesn't.

So the last resort would be to disable pfSense's DNS rebinding check. But I am reluctant to do that.

So if anyone has another solution...?

Thanks

johnpoz

@sensewolf said in Need to convene the brain trust on DNS rebinding issue:

What I am saying is that pfSense should tell server1 server2's private IP when server1 looks for server2.example.com. But pfSense doesn't.

Huh??

If you setup a host override for server2, any client that asks pfsense would get that response..

As already stated if your unbound is getting that address from some other NS, and its rfc1918 then it would be a rebind.. You can set the domain example.com to be set as private, and then it would hand the client the rfc1918 just fine..

example of this plex uses a special fqdn to find the IPs of your server, be it public address and its local rfc1918 address..

So you set this domain as private in unbound custom option box
private-domain: "plex.direct"

And now it can find the rfc1918 address. That it got from public NSers out on the internet