Solved

DNS Issues with Server 2003 - intermitent

Posted on 2009-05-06
6
205 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 500 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
Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

 

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

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

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

Suggested Solutions

Occasionally you run into the website or two that will not resolve properly using your own DNS servers.  Some people simply set up global forwarders for their DNS server.  I don’t recommend doing this because it can cause problems resolving addresse…
Learn about cloud computing and its benefits for small business owners.
This video demonstrates how to create an example email signature rule for a department in a company using CodeTwo Exchange Rules. The signature will be inserted beneath users' latest emails in conversations and will be displayed in users' Sent Items…
A short film showing how OnPage and Connectwise integration works.

932 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

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now