We have a server located in a remote location on our network that can't be
mapped to from our Corporate headquarters using the FQDN or ipaddress
resolved by the corporate DNS server, but from our local headquarters we can
map just fine using the FQDN or ipaddress resolved by our local DNS server.
All of our local headquarter servers including our remote servers are
replicated from our local headquaters to our Corporated headquarters, which
is having problems mapping.This server is clustered so this FQDN is virtual
and can floats back and forth in case the server goes down. It is interesting
that the FQDN and ipaddress of the physical server can be mapped both from
our Corporate headquarters and our local headquarters.

Can anyone please in diagnosing this issue

Thank You,

Netahs
--
cool runnings.