Solved

DNS Resolution Issue

Posted on 2006-06-26
10
267 Views
Last Modified: 2010-03-18
Hello,

Periodically we will have an issue with some, not all of our clients(XP Pro) connecting to the Exchange Server(2003 Standard), sometimes it will be immediately upon booting up or after having being connected all day, they will lose the connection.  They can still access network resources and the internet, but can not connect to the exchange server.  When I ping the internal IP(192.168.x.x) of the exch. server the request times out.  When I ping the hostname(exchangeserver) I get the extertnal IP assigned to the server.  In order to reconnect the affected clients I need to run ipconfig /flushdns and ipconfig /registerdns.  After I run the utility they are connected and when I ping the internal IP(192.168.x.x) it returns the hostname and ping properly.  Please help as this is driving me insane.  TIA

NCIA
0
Comment
Question by:NCIA
10 Comments
 
LVL 57

Expert Comment

by:Pete Long
Comment Utility
Do you have WINS running on anything?
0
 
LVL 11

Expert Comment

by:Eric
Comment Utility
does ip config show they are using a DC as a DNS server?
could there be multiple DHCP server? is your dhcp server configured correctly?

do the users have some type of VPN client?
0
 
LVL 77

Accepted Solution

by:
Rob Williams earned 500 total points
Comment Utility
Workstations should only point to your internal DNS servers for DNS. If you have the ISP's DNS added as well, this could be the issue.
0
 

Author Comment

by:NCIA
Comment Utility
Pete,
I do not have WINS running...

ecszone,
Yes it shows a DC is the DNS server, there is only one DHCP server, as far as I know my dhcp server configured correctly, there are currently no VPN clients installed.

Rob,
I had the primary DNS set up as the internal...and secondary set up as the external(ISP).  If this is the issue why are the clients not accessing the internal DNS first to resolve the querry?  Also if this is the case it seems that they will still lose the connection, just no longer point to the external IP when they do?  I thought that the reason to have the external IP listed was for internet access/resolution.  I have removed the ISP DNS listing to test this idea....

thanks for the ideas....
0
 
LVL 77

Expert Comment

by:Rob Williams
Comment Utility
One would think it would always use the first DNS server first, but for some reason it doesn't always. I don't know if it is a timing issue or what. In any case once it uses the external it likely changes your cashed DNS, and is why you need to run ipconfig /flushdns

Basic rule; the workstations and all servers should only point to your internal DNS server/s and the ISP should be added under Forwarders in the DNS management console.
0
Do You Know the 4 Main Threat Actor Types?

Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

 
LVL 11

Expert Comment

by:Eric
Comment Utility
Yes,
point them ONLY to AD integrated DNS servers.  Let the DNS servers do the lookups.

you should have 2 DNS servers for redundancy also.
0
 
LVL 77

Expert Comment

by:Rob Williams
Comment Utility
By the way once you make the change you should run ipconfig  /flushdns
0
 
LVL 11

Expert Comment

by:Eric
Comment Utility
as a matter of fact, i completly block that port to anyone but my admin workstation, and our DNS servers outgoing. (and all incoming)

I set alerts to warn me if anyone is trying to do DNS lookups.  no reason for clients to do that via default gateway.  Its a good way to keep an eye out for viruses, spyware, etc..

0
 
LVL 4

Expert Comment

by:ansh_gupta
Comment Utility
I think it seems to be a problem with exchange server and the dns. what i would like to know is that output of ipconfig/all of exchange with complete info and error/warnings on exchange server related to dns registration. Also the status of dhcp client service on the exchange server. Please provide me the info
0
 
LVL 77

Expert Comment

by:Rob Williams
Comment Utility
Thanks  NCIA,
--Rob
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

A brief overview to explain gateways, default gateways and static routes OR NO - you CANNOT have two default gateways on the same server, PC or other Windows-based network device. In simple terms a gateway is formed when a computer such as a serv…
Configuring network clients can be a chore, especially if there are a large number of them or a lot of itinerant users.  DHCP dynamically manages this process, much to the relief of users and administrators alike!
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

743 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