Pfsense 2.0 new option
-
BUMP!
-
How about "Resolve DHCP mappings first" ?
No because local DNS names are not necessarily related to anything in DHCP.
-
How about "Resolve DHCP mappings first" ?
No because local DNS names are not necessarily related to anything in DHCP.
What I mean by "that option" is this "Do not use the DNS Forwarder as a DNS server for the firewall". Is this as simple as what I said in my latest post above?
The Resolve DHCM mappings first is another questions, what is that?
-
It does exactly what it says, it resolves DHCP mappings first, before host overrides and such.
-
It does exactly what it says, it resolves DHCP mappings first, before host overrides and such.
Is this the common way to use?
-
It's a matter of preference.
Some people like to have their DHCP system names used no matter what, others want to use the hardcoded entries to override even the DHCP entries.
It depends on the admin and the environment which is preferred.
-
It's a matter of preference.
Some people like to have their DHCP system names used no matter what, others want to use the hardcoded entries to override even the DHCP entries.
It depends on the admin and the environment which is preferred.
Ok, how about "Do not use the DNS Forwarder as a DNS server for the firewall"? Is there a more basic definition?
-
I'm not sure how it can be more clear than exactly what it says. If that is checked, the firewall will not use the DNS forwarder as a DNS server for the firewall.
If it's unchecked, then the firewall will use the DNS forwarder (if it's enabled) to resolve DNS queries, so it can also see the DHCP/static mappings, host overrides, and also queries all DNS servers at once.
-
Thanks.
So the DNS forwarder IP address is localhost?
-
Yes, when it's used by the system itself that's what it uses. The DNS Forwarder listens on every IP on the system though, so it could be any IP, but localhost is always there and never changes, so that's the safest to use from the firewall itself.
