Local FQDN resolution when using DynDNS in DHCP Settings
rarieta last edited by
I'm trying to resolve an internal dns resolution issue. The issue is that when I populate the DNS inside the DHCP settings of a configured vlan, internal FQDN's are being resolved by the DNS set in the DHCP settings.
I have my pfsense box's hostname and domain set in System: General Setup
Domain (protecting my real domain name): somedomain.com
When I receive my vlan specific DHCP address, the dns suffix is set to: somedomain.com
Not using specific DNS in the DHCP settings, I'm able to resolve internal hostnames/ip addresses, however when I set the DNS to a specific DNS provider (ie. google, opendns, dyndns) I'm unable to lookup those internal FQDNs.
I have Enable DNS forwarder on, along with Register DHCP static mappings in DNS forwarder and Resolve DHCP mappings first. This is on "All" interfaces. I have my internal hosts defined in the "Host Overrides" set.
I'm sure this is common, but just not sure what I'm missing to resolve the internals.
who is unable to resolve your internals? pfsense or clients - if you tell your clients to use opendns for example - how would opendns know about your internal something.somedomain.com ?
You should have pfsense set to ask itself - the dns forwarder at 127.0.0.1 and google and opendns if you want it to resolve local names.