FBRemote
asked on
Internal MS DNS resolution problems.. going crazy!
Hi. Recently had a re-ip of a small office. Server A was changed along with all others. Static DNS entries corrected. WINS removed from the environment (all microsoft). Server A is a SQL 2008 R2 server, running a db for an internal app.
We are getting a situation where the internal app launches fine, but at some point, they lose connectivity. If they ping Server A, they get Server B's IP address. an ipconfig /flushdns resolves the issue.
Things tried:
1) shut down WINS/wins services.
2) verified that all DNS servers have the correct static IP
3) verified the client is pointing to the proper dns servers
4) looked in the dns for cname entries
5) used nslookup to show proper resolution when queried.
6) checked local hosts/lmhosts files
7) checked server adapter settings for secondary IP mappings
8) ran arp - a to verify correct macs being returned
Is there any way of finding out, by hostname, what resolution source is responsible? What additional steps can I take to try and narrow this down?
Thanks in advance!
We are getting a situation where the internal app launches fine, but at some point, they lose connectivity. If they ping Server A, they get Server B's IP address. an ipconfig /flushdns resolves the issue.
Things tried:
1) shut down WINS/wins services.
2) verified that all DNS servers have the correct static IP
3) verified the client is pointing to the proper dns servers
4) looked in the dns for cname entries
5) used nslookup to show proper resolution when queried.
6) checked local hosts/lmhosts files
7) checked server adapter settings for secondary IP mappings
8) ran arp - a to verify correct macs being returned
Is there any way of finding out, by hostname, what resolution source is responsible? What additional steps can I take to try and narrow this down?
Thanks in advance!
ASKER
We have now excluded the app from being the culprit. Workstations not running the app are also affected. We are wondering now if it may be a switch issue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: Kaffiend (https:#a41740963)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: Kaffiend (https:#a41740963)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
DNS servers - check
Hosts files on node running the internal app - check
secondary ip addresses - check
etc etc.
Is this problem only manifest on the node that is running the internal app? (Or are all nodes similarly affected?) If so, redouble your efforts there. I suspect maybe the internal app has things hard-coded somewhere.