Not resolving a (duckdns.org) domain that points to a non-public IP
-
What the title says.
I currently have pfsensetest.duckdns.org (created just to illustrate the issue) pointing to 192.168.0.210 and pfSense fails to resolve it.
Using
dig
(from a machine behind pfSense) with the same DNS servers that are set in pfSense resolve it fine. -
@ik13 that would be rebind protection.
https://docs.netgate.com/pfsense/en/latest/services/dns/rebinding.html#dns-rebinding-protections
-
Thank you, sir!
-
@ik13 your welcome - hope your all sorted now. If not happy to help.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.