Solved Unable to access my website

October 7, 2012 at 00:22:14
Specs: Windows 2003, Athlon x2 5gb ram
Hi all, I have a media server, running Windows Server 2003, it is also acting as my Domain controller, DNS and DHCP Server, I have a website hosted at, and I can also access my media server using the name, I have pointed this subdomain to my external IP address of my router, in the Cpanel of my hosting acount now my problem is that I can not access my main website from my house, it just sends me to the login screen of my Media Server, it is something to do with the DHCP Server running on my server, as I turned it off and turned the one on my router back on and it cleared the problem. Does anyone know how to get round this problem


See More: Unable to access my website

Report •

October 7, 2012 at 01:25:46
It cannot be a DHCP server causing this problem (at least not directly). It is clearly a DNS problem. First thing you need to do is to check what DNS server is being used when you get DHCP from your Windows server and what one is being used when you use the router's DHCP. The DNS server being used when you have the problem must have an entry for whatever the URL of your website is pointing at your router's external IP address. So, questions:

1. What is your AD domain name.
2. What is the URL of your website.
3. What DNS server is used when you get an IP address from your Windows server.
4. What DNS server is used when you get an IP address from your router.

Report •

October 9, 2012 at 12:28:13
Hi, My domain name is
and the url of my website is also

my servers DNS address is my ip address of my server, ( I am now thinking this is wrong and it should be using my DNS address from my ISP,

the ip address for my server is

and my ISP DNS address is, should I be using this as my DNS address on my windows server? and using my servers ip address as dns address on my other computers?

thanks or your help

Report •

October 11, 2012 at 03:26:03
✔ Best Answer
Your network computers are looking to your internal DNS server for addresses (which they have to do for Windows networking to work). That DNS server records as the address of your server ( which is not the address of your external web site. Using the same domain name for an internal Windows network and an external public network can lead to this sort of problem.

The easiest solution would be to rename your external web server as and then add an "A" record in your internal server linking with the IP address of the external web server.

Your internal server should list itself as its DNS server, either as or as localhost ( It can then either resolve external addresses directly or, slightly more efficient, be set up to forward queries that it cannot resolve to I forget the exact procedure for this on Windows server, but you are looking for "forwarders" in the DNS Server properties.

Report •

Related Solutions

Ask Question