<div>
I have never run into the problem myself. But, I think I have seen this work well by creating a static HOST A record in DNS, (((((as placebo69 says)))))). But, add the WWW to the host A account so it will route through forwarders or root hint servers.<br />
<br />
xxx.xxx.xxx.xxx &nbsp; <a href="http://www.servername.domain.name" rel="ugc">www.servername.domain.name</a><br />
<br />
where xxx.xxx.xxx.xxx is the outside IP of the server.
</div>


I have never run into the problem myself. But, I think I have seen this work well by creating a static HOST A record in DNS, (((((as placebo69 says)))))). But, add the WWW to the host A account so it will route through forwarders or root hint servers.

xxx.xxx.xxx.xxx   www.servername.domain.name [http://www.servername.domain.name]

where xxx.xxx.xxx.xxx is the outside IP of the server.

<div>
If the domain name has a suffix, such as WWW, you can create an A record that points to the public IP address of the web server.<br />
<br />
If it does not contain a suffix, such as <a href="http://domainname.com" rel="ugc">http://domainname.com</a>, and domainname is your internal domain, I don't believe you will be able to resolve it properly. &nbsp;This is due to your server hosting DNS for that domain.
</div>


If the domain name has a suffix, such as WWW, you can create an A record that points to the public IP address of the web server.

If it does not contain a suffix, such as http://domainname.com [http://domainname.com], and domainname is your internal domain, I don't believe you will be able to resolve it properly.  This is due to your server hosting DNS for that domain.

<div>
<div class="content wysiwyg-content">
I have a domain name that is the same name as the website name (name.com), so I have a domain and a website, but the website is hosted off the domain. &nbsp;When a user tries to get to the website, the DNS server thinks its talking about it and doesnt let through. &nbsp;I have verifed this by pinging the FQDN of the website and the DNS server replies with its (the local DNS server's) IP address. &nbsp;How do i create the passtrough so that a user can get to the website name from internally.
</div>
</div>


I have a domain name that is the same name as the website name (name.com), so I have a domain and a website, but the website is hosted off the domain.  When a user tries to get to the website, the DNS server thinks its talking about it and doesnt let through.  I have verifed this by pinging the FQDN of the website and the DNS server replies with its (the local DNS server's) IP address.  How do i create the passtrough so that a user can get to the website name from internally.

DNS not letting out to website

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).