Link to home
Start Free TrialLog in
Avatar of tl121000
tl121000Flag for United States of America

asked on

DNS ISSUES - LATENCY FROM REMOTE SITE

Our remote site shares the same active directory domain name (abc.com)

Headquarters hosts a few websites, which the remote sites needs to access.

The DNS records on the  the remote site's DNS erver point to the public address of the www housed at HQ.
When the remote site attempts to access, the latency is unacceptable.  However, if a users access the sites from any other location in the world, the sites are served up quite quickly.  Any ideas.

Thanks
Avatar of Paul MacDonald
Paul MacDonald
Flag of United States of America image

Is it possible the remote users are accessing the web site(s) via the WAN connection between the two facilities?  That would make the path "longer" than if they used the local default gateway.
Avatar of tl121000

ASKER

Paulmacd -

This is not a site to site VPN.  To access they need to aces via the Internet.

The gateway set on the clients is the default gateway of the inside interface of the remote router.
Interesting!  Is there anything in DNS that might point them locally first?  

Does the behavior change if the use http://domain.tld versus http://www.domain.tld?
the www record is actually hosted by an ASP and that's fine - the DNS is pointing to the proper public address, as it is for the HQ housed servers.
the other servers are glued to the proper public nat address (i.e. public1.abc.com >>> http://public1.abc.com).
Even if I go directly to the IP address, it is still slow (i.e. http://201.x.x.x)
Looks like there is some kind of routing issues in here.
I assume the site is hosted in head office. you are accessing site from remote site A and remote site B.  
Acess from remote site A is slow.
If you compare the routing to remote site A and remote site B from the head office, it may give some insights.



ASKER CERTIFIED SOLUTION
Avatar of Paul MacDonald
Paul MacDonald
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Sorry for the wait this was resolved some time ago.  It actually was a problem with the ISP.