[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 299
  • Last Modified:

Workstations frequently losing ability to connect to network resources via host name

Hello,

We are assisting a customer internal IT staff with some DNS issues they seem to be facing.  I apologize in advance that I have access to limited information regarding this case but perhaps someone may have suggestions on how to start isolating the source of the problem.

The staff has added an additional DNS server to the network.  It has been configured to replicate with the primary DNS server.

It is now being reported that client workstations occasionally lose host based connectivity to various network resources.  I confirmed that the machines cannot ping the servers hosting these resources by host name, although they are able to successfully ping by IP.  The machines continue being able to access the Internet even when they are experiencing this issue.  Performing an IP renewal addresses the issue, although I do see that the IP remains the same.

I see several of these Events on the primary DNS server:
The DNS server has invalid or corrupted registry parmeter SecondaryServer.  To correct the problem, you can delete the applicable registry value, located under DNS server parameters in the Windows 2000 registry. You can then recreate it using the DNS console.
0
realtimer
Asked:
realtimer
1 Solution
 
kevinhiggCommented:
This sounds like a fun one :)  Presumably if you have the clients use only the primary DNS server (removing the other entry from the IP config), name resolution would work as expected?  A simple test may be just using nslookup to interrogate both DNS servers for one of the problematic names.  Based on your description, and the error message that you've included, it would seem that the secondary config is at very least suspect.

Performing an address renewal on the client allows the busted name to be resolved appropriately?  Or a renewal on the machine that couldn't be resolved previously?  If the former, may be something to do with the local resolver being reset to use primary vs. secondary, or otherwise modifying the cache.  The 2nd scenario could be indicative of aged records being scavenged inappropriately, or ...  Good luck!
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now