dns hostname not resolving lan server ¿

strange thing happened this morning:
all of a sudden one of our servers cannot be addressed by its name 'bertha' the hostname resolves to bertha.com.au(or its IP address) (must be a new website created) instead of the servers LAN IP address 192.168.2.3.

we have 2 sites both with a DNS and DHCP server. I check both the forward and revese lookup up zones on the 2 sites and the site not resolving the IP had the PTR entry missing so I added the entry. that didn't help.

Keeping in mind that alll servers have been working untouch for a few years, this new problem arised today for only one server.

What can be wrong for a hostname to resolve to an internet address instead of its LAN address ?
siacomAsked:
Who is Participating?
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.

ecsrdCommented:
On the system that is unable to resolve the hostname, is it using an appropriate DNS server that SHOULD resolve the internal address?
0
siacomAuthor Commented:
yes it is. there is also a WINS and DHCP server on it with routing rules.

This problem suddenly arose overnight, probably by the new existance of bertha.com.au.

All other computers and server resolve hostname propely.
I have just restarted the DNS server that doesn't resolve properly after making one change. I simply remove the PTR record and recreated it to see what happens....

0
siacomAuthor Commented:
no luck so far ... stilo the same.
0
ON-DEMAND: 10 Easy Ways to Lose a Password

Learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees in this on-demand webinar. We cover the importance of multi-factor authentication and how these solutions can better protect your business!

ecsrdCommented:
Check the WINS configuration, since you are using shortname to lookup the server, WINS would be used by default (or NetBIOS on the same subnet).
0
siacomAuthor Commented:
yes WINS is used and the entry for bertha with the correct IP is listed..I will do a few scren captures of DNs WINs and DHCP of the relevant entries.
0
ecsrdCommented:
Are the WINS settings set for the network cards on the affected stations?  Is the WINS server responding to requests?
0

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
siacomAuthor Commented:
I'm having a look at the WINS config now... it does have the other domain entry as a replication partner.
0
ecsrdCommented:
Let me know what you find.
0
siacomAuthor Commented:
ok the problem is gone... and I don't really know exactly what fixed it, maybe a corrupt entry on the DNS server having the problem.

I deleted all DNs entires on that server only that had references to bertha waited a couple of minutes, recreated the entries, restarted the DNS server, restart the DNS and WINS server waited a couple more minutes then pinged... all is ok now. ¿ ? ¿


0
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
Internet Protocols

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.