Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

DNS Issues with Server 2003 - intermitent

Posted on 2009-05-06
6
Medium Priority
?
249 Views
Last Modified: 2012-05-06
I have 3 domain controllers all do DNS and DHCP for their range. The main DC does not want to resolve names or gives me internment DNS issues.

For example if I reboot the main DC it takes forever to come up first of all and it's a fairly new machine. Second DNS works like a champ for an hour or two then goes to hell. If the DNS record is for a remote location like another office on the WAN, I can no longer ping it by name on my desktop. I have to use the IP. If I flush my DNS and register all is well for a bit again.

Another issue is the DNS seems to work fine after the DC is rebooted for people coming in on our VPN. However after the DC has been up for an hour or two you can no longer resolve things via the name when you VPN in. Restarting the DNS services does no good.

Everything works great once rebooted for a small period of time
0
Comment
Question by:Prez2510
  • 2
  • 2
  • 2
6 Comments
 
LVL 26

Expert Comment

by:jar3817
ID: 24317506
Do you have any external dns server listed on these 3 servers? You should only have the DC's set as dns server on all workstations and servers (including the DCs themselves)
0
 
LVL 6

Accepted Solution

by:
ilantz earned 2000 total points
ID: 24317651
each DC should have their dns settings in tcp/ip pointing to themselves first :
127.0.0.1 , 2nd and above should be other dc's.

check your settings on clients computers and the forwarding settings on each DC as Jar3817 said.

another thing , did you perhaps install SP2 for server 2003 lately on the dc's?
0
 

Author Comment

by:Prez2510
ID: 24317713
On the NIC for that server?
0
WatchGuard Case Study: NCR

With business operations for thousands of customers largely depending on the internal systems they support, NCR can’t afford to waste time or money on security products that are anything less than exceptional. That’s why they chose WatchGuard.

 

Author Comment

by:Prez2510
ID: 24317724
They have had SP2 for a long time. Let me try the DNS things it looks like there is an external listed
0
 
LVL 26

Expert Comment

by:jar3817
ID: 24317755
Check all nics if you have more than 1. If you want to use your ISP or some external server as an upstream nameserver, set it up as a fowarder, don't list it as a resolver for the whole system.
0
 
LVL 6

Expert Comment

by:ilantz
ID: 24317808
DC's should always always always point to themselves first :) yeah
never point directly to external dns servers , nor in clients either ..

unless of course you're testing or anything ..

good job.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

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

On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
A quick step-by-step overview of installing and configuring Carbonite Server Backup.
This Micro Tutorial will teach you how to add a cinematic look to any film or video out there. There are very few simple steps that you will follow to do so. This will be demonstrated using Adobe Premiere Pro CS6.
Want to learn how to record your desktop screen without having to use an outside camera. Click on this video and learn how to use the cool google extension called "Screencastify"! Step 1: Open a new google tab Step 2: Go to the left hand upper corn…

927 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