DNS Name resolution

[Jeff]

hi all,

for some reason the url www.crossflow.com resolves to
66.54.199.45 internally (which is wrong) and to
66.124.118.11 externally (which is correct).

I naturally think its a DNS error, but I don't see it
anywhere in DNS. I the cache has it incorrect, so I
clear it and it keeps coming back.

What is the protocol for the name resolution? Is there a
way to verify each step? How would I check to see that my
external DNS is resolving correctly (since the internal
forwards to there)

Thanks.

- jeff

 

[Guest]

If you want to check,

nslookup
server external.DNS.IP
www.crossflow.com

BR,
Denis

 

[Ace Fekay [MVP]]

In

hi all,

for some reason the url www.crossflow.com resolves to
66.54.199.45 internally (which is wrong) and to
66.124.118.11 externally (which is correct).

I naturally think its a DNS error, but I don't see it
anywhere in DNS. I the cache has it incorrect, so I
clear it and it keeps coming back.

What is the protocol for the name resolution? Is there a
way to verify each step? How would I check to see that my
external DNS is resolving correctly (since the internal
forwards to there)

Thanks.

- jeff

That "incorrect" IP resolves to:
Name: mail.develligent.com
Address: 66.54.199.45

Are they affiliated with your org? Does this happen on all machines or just
one? If just one machine, check your hosts files for hijacking.

Otherwise, its apparently coming from somewhere. What IP ranges are
internal? Are they private? Do you have a www record internally created with
that IP?

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.