In this Video we will: 

• We will illustrate how DNS Forwarding can work in your organization.
• We will consider a common scenario in which DNS forwarding can be deployed.
• At the completion of this lecture you will gain valuable-work related knowledge and experience by utilizing and implementing the steps given in this lecture.

Prerequisites: You must have access to or have installed in your lab the following: 

• One Windows 2016 Server with Active Directory installed and promoted to a domain controller (DNS installs automatically).
• Or a VM with the identical configuration.
• Don’t forget to download the supplemental information that I have supplied with this lecture.

Adequate permissions will be needed 

• To configure a DNS server that is running on a domain controller, you must be a member of the DNS Administrators, Domain Administrators, or Enterprise Administrators group.

So what is forwarding?  And how are forwarders used? 

A forwarder is a DNS server on a network that forwards DNS queries for external DNS names to DNS servers outside that network.

We will illustrate how forwarders are implemented using a typical scenario:  Let’s say for discussion purposes we have a user named Joe, and Joe has an office computer named dellpc.  

• Joe opens his browser and tries to access foxnews.com. Joe’s company has a DNS server named DNS1.  

Here is what is happening between Joe’s browser and the DNS server DNS1.

1. Dellpc sends a recursive query to DNS1 asking DNS1 to resolve foxnews.com into its associated IP address. DNS1 checks its local cache, then it’s data base,and finds zone information for only bus.dns.local domain not finding foxnews.com.
2. DNS1 uses its root hints file and sends an iterative query to the first available Internet Root server.  
3. Which responds with the IP address of a name server authoritative for the .com top-level domain.  
4. DNS1 sends a second iterative query to the name server authoritative for .com.  
5. This server responds with the IP address of a name server authoritative for the foxnews.com.domain.
6. DNS1 sends a third iterative query to the name server authoritative for foxnews.com.and  
7. This server responds with the IP address for foxnews.com.
8. DNS1 returns the IP address of www.foxnews.com.to dellpc and Joe sees foxnews.com.appear in his browser’s window.

That is a lot of processing going on! What if the company had a slow WAN link. Now you are wasting valuable bandwidth. Think with me for a minute. If there are 500 users all sending queries to the local DNS server for various internet sites outside the local network, you could definitely understand how DNS1 could get bogged down with DNS requests.  

We ask this question, is there a better way than always going to the root server for answers to our queries? Why not create a forwarder to the ISP’s DNS server.

Let’s see how configuring a forwarder to our ISP’s DNS server would play out in our scenario.

1. Dellpc sends a recursive query to DNS1 asking DNS1 to resolve foxnews.com into its associated IP address. DNS1 checks its local cache not finding foxnews.com.
2. Then because forwarders always take precedence over the server’s root hints file, DNS1 checks its list of forwarders to see if any forwarders have been configured to help resolve the query. On the forwarders list DNS1 finds the IP address of the external name server hosted by the company’s Internet Service Provider, so it forwards the query to the ISP’s name server.
3. The ISP’s Name server goes up to the root server as needed (which results in several more iterative queries.
4. Finally, the ISP receives an answer and resolves www.foxnews.com into its IP address.  
5. The ISP returns this address to DNS1.
6. DNS1 returns the IP address of www.foxnews.com.to dellpc and Joe sees foxnews.com.appear in his browser’s window.

Server Academy Members Only

Sorry, this lesson is only available to Server Academy Full Access members. Become a Full-Access Member now and you’ll get instant access to all of our courses.

Sign In Get Instant Access