Server 2012 R2 DNS Conditional forwarding not working reliably, possible caching issue?

Posted by Matt on Server Fault See other posts from Server Fault or by Matt
Published on 2013-10-28T07:23:14Z Indexed on 2013/10/28 9:55 UTC
Read the original article Hit count: 299

I have a bit of a home lab setup with a domain controller that is acting as the DNS server for my network. For everything, it's working fine and forwards external DNS requests to my ISP. The household recently wanted to get Netflix going and it seemed a DNS option was better than a VPN to get around the region locking, so I signed up for unblock-us.com

Since I have a Windows DNS server I thought I'd be clever and make use of conditional forwarders and added the Netflix domain to the list. Initially this worked well and all devices on the network could now access Netflix, however after about an hour going to the Netflix site would result in a page cannot be found. Doing an nslookup of Netflix.com from my PC resulted in it not returning any IP addresses. As a test, I deleted the Netflix domain from the DNS servers cache and things started working again - devices could get to the site again however the same thing happens again after around half an hour to an hour.

Have I missed something here that's causing it to stop working?

© Server Fault or respective owner

Related posts about dns

Related posts about forwarding