PartlyDave
MIS
I'm receiving complaints that users can't get to out company’s web site without including the "WWW" in the address. We host our own site within our DMZ. This is a W2K Active directory domain. The web domin name and the active directory domain name are the same, "domainname.com"
Actually they can get to the site without including the the url, but it's very slow to bring up the site. If they enter http:\\ the site appears instantly, if they just enter http:\\domainname.com it takes 30 seconds or more for the site to appear in their browser.
I have a host name entry for DNS in the "doaminname.com" zone that points to the address of the web server.
I can see that if the web domain name and the AD domain name were not the same I could simply put in a DNS record for "doaminname.com" just like I did for "
So, how do I improve name resolution speed for those users who insist on dropping the WWW?
Actually they can get to the site without including the the url, but it's very slow to bring up the site. If they enter http:\\ the site appears instantly, if they just enter http:\\domainname.com it takes 30 seconds or more for the site to appear in their browser.
I have a host name entry for DNS in the "doaminname.com" zone that points to the address of the web server.
I can see that if the web domain name and the AD domain name were not the same I could simply put in a DNS record for "doaminname.com" just like I did for "
So, how do I improve name resolution speed for those users who insist on dropping the WWW?