Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 581
  • Last Modified:

WPAD CNAME

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
stowyo
Asked:
stowyo
1 Solution
 
Will SzymkowskiSenior Solution ArchitectCommented:
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
 
ChrisCommented:
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
 
stowyoAmericas Regional IT ManagerAuthor Commented:
Good answer.  The command is:

run
dnscmd /config /enableglobalqueryblocklist  0
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now