We currently have a forward lookup zone setup on our domain controller. This redirects are users when they open a browser and go to www.projectsetup.com. The redirection takes them to our own internal site. It has worked great for a year or so. Then, yesterday - we noticed that some users stared having the issue of going to www.projectsetup.com and actually getting to the external site on the internet. Typically a reboot of their PC would fix this, but what would cause it? It is now an ongoing issue. I checked and made sure that users having the issue and users not having this issue are all authenticating to the same DC - that is, this one with the Forward Lookup Zone pointing to our in-house web server and website.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Maybe check their cache?
-You can check the problematic workstations by using "ipconfig /displaydns" in the command prompt
If there are any entries in there for www.projectsetup.com - that aren't your local server, this could be your problem
-You can clear the DNS cache by using "ipconfig /flushdns" in the command prompt on the workstation
After authentication to the DC, a computer can still use any DNS server that it's configued with. All the DNS servers listed under "ipconfig /all" has to have the entries. And in an AD environment, they all should since DNS is replicated with AD. Do you have any non-AD DNS servers in your org?
If you want to see exactly how the DN is getting resolved, go to a machine that is not working and type
"nslookup -d2 www.projectstartup.com" The results can be a bit confusing, but if you look at it long enough, it should make sense.
An altenative is to push a HOSTS file that includes a static entry.
I ran nslookup -d2 www.projectsetup.com on two computers. One that was properly authenticating to the internal website when attempting to go to projectsetup.com (desired result), and another that was getting out to the internet site when attempting to get to projectsetup.com (not the desired result).
I printed out the results of these nslookups and compared the two. They are virtually identical in very single way. The only difference is the serial=xxxxx under the AUTHORITY RECORDS section, and I am not sure this is a relevant difference.
Thoughts? I can post these results if that helps.
Before I do that, I think I may have fixed it. Based on your statement "all DNS is replicated with AD", I did some poking around in DNS on our three DC's (all DNS servers). The forward lookup zone we have for projectsetup.com was present in 2 of the 3 servers. I was able to replciate the zone over to the server that was missing it by allowing zone transfers for this zone to this specific server that was missing it. It appears to have corrected this issue - but I wondered, shouldn't all zones on the primary DC be setup to allow zone transfers to all other DC's (or rather DNS servers) on the network? Or should all zones be automatically replicating with AD anyway without zone transfer allowance specifically setup (because it wasn't).
When you setup DNS on a Domain Controller, it gives you the option to "store DNS database in Active Directory" (or something like that). You basically should always select this option unless you know otherwise.
My guess is that you have a Primary Zone configured on that server but it is not being stored in Active Directory.
On that server, go to the DNS console and right-click the domain under the Forward Lookup Zone section and choose 'properties'. On the general tab it should have a place to change the "Type" and "Replication". The type should read "Active-Directory Integrated" and the replication should read "All Domain Controllers in the AD domain"
Business Accounts
Answer for Membership
by: jar3817Posted on 2008-01-11 at 07:41:34ID: 20637255
What nameservers are you pushing out via DHCP? Are they only internal ones or do you have ISP servers also? If they're getting external addresses, they probably have a setting for an external dns server.