compsol1993
asked on
Win 2k3 Server DNS - Offsite Website
Hello,
We have several clients who have SBS 2003 servers, with names like mail.domainname.com
In order to properly find the mail server inside of the office, we've setup a DNS entry in the SBS servers DNS tool. There are usually two Host entries there mail.domainname.com resolves internally, to the internal IP of the mail server. The second is www.domainname.com, which resolves to the external IP of the company's website.
In each case the site is hosted offsite. In the past, all we've dealt with are websites with dedicated IPs, and this has always worked. Our latest server has a website hosted on a shared IP.
Thus a client inside the network cannot reach the site, instead of going to the site, it does not find anything, in the same way it wouldn't find anything if I entered the "Shared IP" directly into my browser.
Is there something more I need to add to the Win 2k3 DNS tool aside from creating a host for "www"?
We have several clients who have SBS 2003 servers, with names like mail.domainname.com
In order to properly find the mail server inside of the office, we've setup a DNS entry in the SBS servers DNS tool. There are usually two Host entries there mail.domainname.com resolves internally, to the internal IP of the mail server. The second is www.domainname.com, which resolves to the external IP of the company's website.
In each case the site is hosted offsite. In the past, all we've dealt with are websites with dedicated IPs, and this has always worked. Our latest server has a website hosted on a shared IP.
Thus a client inside the network cannot reach the site, instead of going to the site, it does not find anything, in the same way it wouldn't find anything if I entered the "Shared IP" directly into my browser.
Is there something more I need to add to the Win 2k3 DNS tool aside from creating a host for "www"?
ASKER
Thanks for your input.
Unfortunately that doesn't work either.
To make sure nothing else was going on, I temporarily removed that Forward Lookup Zone from my DNS server, allowing the domain to resolve using our ISP's servers, and the site works fine.
Aside form the concept of host headers, what else would need to be done from our end. I've double checked that I have the correct Shared Hosting IP.
Thanks
Unfortunately that doesn't work either.
To make sure nothing else was going on, I temporarily removed that Forward Lookup Zone from my DNS server, allowing the domain to resolve using our ISP's servers, and the site works fine.
Aside form the concept of host headers, what else would need to be done from our end. I've double checked that I have the correct Shared Hosting IP.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well, the reason for the lookup zone was when people with smartphones were inside of the office, and connected to internal wifi, they would lose their connection to the server, as the mail.domainname.com wasn't resolving inside.
But you are correct, this is our public name, not the name of our internal domain or active directory.
I'll have to setup a time to test with the nslookup, thanks for that input.
But you are correct, this is our public name, not the name of our internal domain or active directory.
I'll have to setup a time to test with the nslookup, thanks for that input.
Try this:
Add a blank Host A record in the abc.com forward lookup zone that points to the web server address. Then browse to abc.com only (without the WWW). Let me know if that works.
If it does, you should ask the hosting company to configure host headers for www as well on the site.