Solved

DNS Issues with Server 2003 - intermitent

Posted on 2009-05-06
6
222 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
Space-Age Communications Transitions to DevOps

ViaSat, a global provider of satellite and wireless communications, securely connects businesses, governments, and organizations to the Internet. Learn how ViaSat’s Network Solutions Engineer, drove the transition from a traditional network support to a DevOps-centric model.

 

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

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

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

Resolve DNS query failed errors for Exchange
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

821 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