| Server 2003 DC Deployment - DNS Forwarders |
|
|
|
| Written by Tom Hirt | ||||||
| Friday, 08 May 2009 09:38 | ||||||
Page 3 of 4
DNS Forwarders
Now that we have prompted our domain controller, we need to configure DNS forwarders to help with external name resolution. Thus far, internal name resolution will be handled by our domain controller/DNS server but how do we handle the Internet?
The answer is simple, we configure a DNS forwarder on our DNS server. DNS forwarders forward queries for unknown domains to other DNS servers for name resolution and cache their responses based on the TTL (time to live) value set with the associated record. So in other words, if our DNS server doesn't know the address for say, www.google.com, then it will ask a downstream DNS sever (a forwarder) if it knows the address. The downstream DNS server intern performs the same lookup and forward the query on if it doesn't know the address for the host. This process repeats itself until your query either hits a DNS server with a cached response (the TTL hasn't expired for the record) or your query finds its way to the SOA (start of authority.) The answer is then returned along the same path with a TTL value so that it may be cached for quicker subsequent look-ups. Typically you will set your DNS forwarders to your ISP's DNS server(s). Your ISP should provide you with the address(s) for their public DNS servers. In the following example, we will set our DNS servers to TCPDump's ISP's DNS servers, but you should make certain to replace the address from our example with your ISP's DNS servers as you'll most likely not have access to query our servers.
|
||||||
| Last Updated on Tuesday, 02 June 2009 11:05 |