Solved

WPAD CNAME

Posted on 2013-06-24
3
563 Views
Last Modified: 2013-06-25
Hi - We have a WPAD CNAME that will only resolve on our original DC's around the globe.  ANy new DC's full or RODC, the CNAME for WPAD will not resolve.  Very strange issue.  Please help.

Server 2008 R2 across the board - combination of VPN site to site links and MPLS.
0
Comment
Question by:stowyo
3 Comments
 
LVL 53

Expert Comment

by:Will Szymkowski
ID: 39273385
The DC's you are deploying have DNS? I would assume yes, if this is true, can you open the DNS console on one of the new DC's and see if that CNAME record exists? Also, have you checked your firewall settings on these machines to ensure they are correct?

Also, instead of pointing the DC to itself for DNS, if you point it to one of the old DC's do and ipconfig /flushdns and try pinging the cname again does it work?
0
 
LVL 18

Accepted Solution

by:
irweazelwallis earned 500 total points
ID: 39274234
have you made sure that WPAD is allowed on via the blocklist and that setting is on all the DC's

http://technet.microsoft.com/en-us/library/cc995158.aspx
0
 
LVL 1

Author Closing Comment

by:stowyo
ID: 39274619
Good answer.  The command is:

run
dnscmd /config /enableglobalqueryblocklist  0
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I've written instructions for one router type, but this principle may be useful for others of the same brand and even other brands of router. Problem: I had an issue especially with mobile devices that refused to use DNS information supplied via…
This article runs through the process of deploying a single EXE application selectively to a group of user.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question