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!
FBRemoteAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

KaffiendCommented:
Looks like you have already covered most of the bases:
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.
FBRemoteAuthor Commented:
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.
KaffiendCommented:
It's a name resolution problem, so not likely to be a switch issue
(ping server A by name, get server B's IP address, right?  and strangely enough, ipconfig /flushdns fixes it at least temporarily)

I know you said you've checked the DNS servers, but from what you're saying, it seems that is the place where something is wrong.  Check the zones in each individual DNS server would be my guess

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Seth SimmonsSr. Systems AdministratorCommented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
TCP/IP

From novice to tech pro — start learning today.