<div>
If your internal webpage is <a href="http://server1" rel="ugc">http://server1</a>, is the server1 resolving to the correct IP which has IIS running? You could check it in DNS or just do a ping server1 and see what IP it is resolving to.
</div>


<div>
That's the thing, when I ping our domain sometimes it resolves to the correct IP and sometimes it goes to the incorrect DNS server.<br />
<br />
Even if a machine has static IP information and it's DNS server is set to 10.1.1.30 which is correct, sometimes when I ping our domain name it resolves to 10.1.2.50 which is not correct.<br />
<br />
It's like in DNS somehow they are both listed when only 1 should be listed. &nbsp;Can I remove DNS completely from the 2003 Backup DC?<br />
<br />
M.
</div>


<div>
Is 10.1.2.50 your 2003 Backup DC? <br />
<br />
And again in 2003, all DCs are the same, multi master model. There is no harm in having DNS on the server as it will give redundancy. Check in DNS server to find out whether 10.1.2.50 is pointing to any server? 
</div>


<div>
I can't really duplicate everything because I would have to install Exchange, Moodle, PHP, MySQL... just not feasible.<br />
<br />
I thought this happened before and I deleted a host record for the domain somewhere that pointed to 10.1.2.50 and then everyone was directed to the correct IP 10.1.1.30.<br />
<br />
Just need to make it so any traffic internally bound for our web domain gets routed to 10.1.1.30.<br />
<br />
M.
</div>


<div>
<br />
Okay, duplicating the site was a bit of a long shot unless it were plain html. Deleting the second host record works, right up until the point the second DC registers it again.<br />
<br />
In all seriousness changing the name used to access the site is by far the simplest solution. Trying to work around AD needing that name is going to be painful.<br />
<br />
Chris<br />

</div>


<div>
Thanks guys,<br />
<br />
Yeah I had to set everyone's outlook up using servername.domainname.com about a year ago. &nbsp;Using the IP does work fine for the website, only thing is OWA says the SSL certificate does not match if you use the IP because it was created using the domain name. &nbsp;It still works, it just makes people ask me what the error message means.<br />
<br />
M.
</div>


<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
I work at a school and after having our primary DC have some issues a while back I setup another of our 2003 servers to handle DNS as well and Active Directory so if we'd have some redundancy.<br />
<br />
Our schools webpage is hosted on our DC / Exchange Server / DNS Server. &nbsp;This machine is 10.1.1.30.<br />
Well, occasionally when I'm at the school and we try to access the schools webpage internally it goes to 10.1.2.50 which is the BDC which also runs DNS. &nbsp;Of course the webpage never loads because this machine doesn't run IIS. &nbsp;No Outlook Web Access because it's not running exchange...<br />
<br />
The client machines with the problem are pulling the correct DNS server 10.1.1.30 and all other settings are correct as well.<br />
<br />
How do I make sure our domain name always points to 10.1.1.30 internally?<br />
<br />
Thanks,<br />
<br />
M.
</div>
</div>


Hello,

I work at a school and after having our primary DC have some issues a while back I setup another of our 2003 servers to handle DNS as well and Active Directory so if we'd have some redundancy.

Our schools webpage is hosted on our DC / Exchange Server / DNS Server.  This machine is 10.1.1.30.
Well, occasionally when I'm at the school and we try to access the schools webpage internally it goes to 10.1.2.50 which is the BDC which also runs DNS.  Of course the webpage never loads because this machine doesn't run IIS.  No Outlook Web Access because it's not running exchange...

The client machines with the problem are pulling the correct DNS server 10.1.1.30 and all other settings are correct as well.

How do I make sure our domain name always points to 10.1.1.30 internally?

Thanks,

M.

Question about DNS on a Windows 2003 BDC

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).

Windows Server 2003

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.