<![CDATA[nip.io behind unbound on pfSense]]>I could need nip.io working in several LANs I run behind pfSenses.

It doesn't work out of the box, because pfSense does some kind of DNS rebinding protection:

gh issue

Has anyone managed to make this work without having to run a local nip.io instance and to edit local systemd-resolved config?

]]>https://forum.netgate.com/topic/196818/nip-io-behind-unbound-on-pfsenseRSS for NodeMon, 13 Jul 2026 21:55:24 GMTMon, 17 Mar 2025 14:42:29 GMT60<![CDATA[Reply to nip.io behind unbound on pfSense on Mon, 17 Mar 2025 15:09:28 GMT]]>@johnpoz wow, great, thanks for the quick help! works already, wonderful.

]]>https://forum.netgate.com/post/1209512https://forum.netgate.com/post/1209512Mon, 17 Mar 2025 15:09:28 GMT<![CDATA[Reply to nip.io behind unbound on pfSense on Mon, 17 Mar 2025 15:05:31 GMT]]>@sgw

Yeah that would be rebind

test-192.168.1.1.nip.io.

Set that as private domain in your unbound config.. And then it would resolve.

nipio.jpg

Any time unbound asks, forwards to another NS and answer is rfc1918 that would be considered a rebind, so you have to tell unbound hey rfc1918 for this domain is ok.. See how have plex.direct in mine - it does the same sort of thing.

]]>https://forum.netgate.com/post/1209510https://forum.netgate.com/post/1209510Mon, 17 Mar 2025 15:05:31 GMT