DNS Resolution Behavior
-
Could anyone explain this option in practical terms?
I have a basic home server here, so this is not a corporate network, meaning there is no local DNS server.
I don't quite understand the relationship between this and the DNS Resolver.
In my case, should I change the former into "use remote, ignore local DNS"?
As you can probably tell, I am no networking expert whatsoever. -
Throw What is a DNS Resolver ? in your favourite search engin, and pick the explanation your conformable with.
You've heard about 1.1.1.1 and 8.8.8.8 ? These are resolvers.A resolver knows how to contact the 'main' Internet domain name index (see them as a huge phone book) and can resolve any exiting host name into an IP.
A "DNS server", like bind, can do more, like offering domain name serving, which isn't really the role of a firewall router like pfSense.
-
This post is deleted! -
@octopuss My understanding is;
-
DNS server follows the domain name delegation hierarchy to determine any specific domain name you request. Starting at he least specific part of the name "." then working to the left. Contacting authoritative name servers for each level in turn. As a result no other DNS is specified by the user when this is set up.
-
DNS resolver asks another DNS server any Domain name you request. As a result another DNS server must be specified when the resolver is set up.
-
Both cache domain names.
But I may well be wrong. The major difference maybe the DNS server can be an authoritative Domain name server for the domain you host.
-
-
@patch Uh, complicated. I'll leave it at default then.
