Terms of Use For FixedByVonnie

By proceeding to access fixedByVonnie.com, you expressly acknowledge, and agree to, all of the following:

fixedByVonnie.com is a personal website and blog owned by Security Plus Pro LLC, which is being presented for informational purposes only. The views on this website are solely those of the website owner (and not those of any employer or of any professional associations affiliated with the website owner).  Any views expressed in this website and any information presented on this website, or in any of its blog entries, should not be relied on for any purpose whatsoever other than as the personal opinions of the website owner.  The website owner expressly disclaims any and all liability for any information presented on this site.  The owner of this website and its blog posts shall not be held liable, and shall be held harmless, for any errors or omissions in any information or representations contained in this website, or in any of its blog entries.  The website owner also expressly disclaims any liability for the current or future availability of any such information. The website owner makes no representations as to the accuracy or completeness of any information on this website or which may be found by following any link on this website. The website owner shall not be held liable for any losses, injuries, damages, claims, or causes of action, from the display or use of any information on this website or in any of its blog entries. If you use the information on this website, or on any of its blog entries, you do so solely at your own risk.

Configuring DNS Forwarders in Windows Server 2016 - fixedByVonnie

Configuring DNS Forwarders in Windows Server 2016

Last time we go together, we looked at installing the DNS server role to your Windows 2016 server.  Now we’re going to dive into configuration baby!

To configure the DNS forwarder (so it can resolve names it doesn’t have cached or in its zone file) we need to open the DNS manager.

So hit the Windows Logo key on your keyboard, type “Server Manager” and then choose “DNS” from the Tools drop down menu in the upper-right corner of the screen.

DNS manager Windows Server 2016

Yeah, I know it looks like nothing is going on here but there’s a magical world hiding under that FBV-DNS host in the left pane… check this out.

Windows Server 2016 DNS Manager

Right click the hostname go to Properties

Windows Server 2016 DNS Manager Properties

Hit the Forwarders tab, click the Edit button to prepare to add a DNS server that can resolve names for us.

DNS Forwarders in Windows Server 2016

We’ll add to resolve the addresses.

Adding our DNS forwarder to Windows Server 2016

So to test this we’ll type ping youtube.com from our Windows 10 client machine.

This will force our local computer to check its %WinDir%\System32\Drivers\Etc\hosts file for static entries and then its local cache for an A record mapped to the youtube.com domain name.

We can take a look to see if there’s a mapping already with the following command:

type %windir%\system32\drivers\etc\hosts | findstr youtube.com

Alright nothing there.

Check the host file

So now we can check the local DNS cache

ipconfig /displaydns | findstr youtube.com

So we have no mappings right now.

Check the local DNS cache


Let’s ping youtube.com and then check the local DNS cache.

Basically what happened is the client said:

Yo, DNS server, I need you to give the IP address of youtube.com.

So our local DNS server, the Windows 2016 Server was like, “let me check my host file and my local cache… dang… I have no idea let me forward this request up the chain”

This is called a Forward Lookup request and the DNS server made a forward lookup request for the A record belonging to youtube.com.  Since we configured as the forwarder, took care of it.

That Google DNS server,, looked up the name, replied to the Windows 2016 Server with the answer, the 2016 server cached the response and then forwarded the reply on to the client which can then cached the result as well.

So we need to view the DNS cache.

On our Windows 10 machine we can type:

 ipconfig /displaydns

ipconfig /displaydns

And on the server we can type:



You can see the DNS cache record there.

And if you want to see what’s happening at the packet level just check this out:

DNS queries at the packet level

I took this from the client.  You can see the client ( sending a DNS query to our Windows 2016 server ( with the query of Type: A for youtube.com.  This is in the middle pane.

So the Windows 2016 Server received the query, forwarded it along and then sent back the response it received from

DNS response

Pretty cool eh?

That’s all there is to it.


Connect with Vonnie on Twitter

Posted in Windows Server