Windows Forum

Ask something
Discussion Locked

DNS Names

0 helpful
12 replies

by sturner

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Ok here si the issue. When doing a ping or such type lookup an ip use to report back a name correctly as an example: TPAPC01.

But now suddenly we get back wierd names like:
ACA80337.ipt.aol.com

I cant figure this one out. I have checked my internal DSN and WINS and everything looks good there. All users are pointed to the correct DNS server via DHCP. The only change that was made to the network prior to this starting was we switched form DSL to a Full T-1, but I still can't figure out how that would cause this issue, when the internal DNS server does not rely on the ISP whatsoever!

Help me!!!!!!

12 replies

by stan

Does the DNS server have a static IP or is it using DHCP. You may have to reconfigure the IP address on the server. You should contact you ISP for the correct IP information.

by sturner

The DNS server in question is an internal DNS server that resolves for my network domain. If it can not resolve the it forwards to the ISP's caching DNS server. When we switched to the new ISP the frowarder was changed to reflect the NEW ISP's DNS IP!

Thanks and hope you can help further!

by bkinsey1

Are you using publicly routable IP addresses on your internal network, or private IPs? What happens when you do a traceroute of an IP that comes back with an unexpected name? What happens when you T-1 connection is down and you ping the same name? Do you get the proper response?

I'm wondering if your DNS server is timing out or not responding for whatever reason, and the requests are going out to your ISP's DNS. If the IPs are public, that DNS server would then go up the DNS chain until it found a machine somewhere with that address. Of course, it that's really happening, then either you or the other machine is using an address you shouldn't be using, but that's about the only thing that occurs to me right now. *shrug*

by sturner

We are using a private 172.168 class b network. When I do a tracert it is a one hop ping directly to the system but reports the funky name. I can not take down the T-1 to test if it was down, but it does not appear to be leaving the network to resolve because I am doing my tracert by IP. I can also do a tracert by name (i.e TPAPC01) and it reports the proper ip but shows the hop destination as the funky name.

But it does appear that internal resolution is working and I am on a private ip network.

by mjost

Have you performed a ipconfig /flushdns on w2k or newer? I had this type of problems when I change from one internet provider to another.

by sturner

I would have to say that this has appeared to fix the issue T-15 mins...... I appreciate you trollg the old issues as I did not think this one woule be looked over again. POints to you good sir!

This discussion is closed to new replies.