MonitorWare Knowledge Base

I installed AD, with the name of binarydreams.us (which is also mywebsite). I disabled DHCP on my cable router(192.168.2.1), and installed DHCP on my DC, and everything works fine. The users can log on, get all the IP and DNS info from the DC, they could load web pages, etc.

But, if they go to www.binarydreams.us it instantly comes up with: host not found. I cant even ping the website.

I assume that it has to do with my AD namespace. I read that you can have either the naming convention be the same as your external site and not allow the public to see the internal.. Which I wanted to. But I have no idea what to do to allow my internal users to see my website... any ideas?

The reason why you can't access your external site is, that your own DNS Server holds this domain. And I assume there is no host entry definied for "www".

To describe the problem, your internal Clients queries for the host "www" from the domain "binarydreams.us" from their default DNS Server.
I also guess this is the Windows 2000 machine which holds the ActiveDirectory. So it queries the host from the ActiveDirectory zone, and not that from the internet.

The following article might help you to solve the problem:
http://www.windows-expert.net/Common/en ... Access.asp

If not, you have two chioces. Either add an "www" host entry which points to the right Webserver Address.
Or rename the ActiveDirtory (This is not very easy) and use a sub zone like internal.binarydreams.us.

I thought of renaming the domain, but I'd like to have the domain to be my website name.. That article that you linked, I have the "." pointer deleted, and now I have to enable the forwarders? Do I put in my hardware routers IP address? (remember DHCP is dissabled). All the router does is act as the gateway. The routers IP is 192.168.2.

btw, I like your forum software... I use phpbb also

Hi,

yes phpbb is very cool I love it, too.

Regarding your problem, you either have to find out which DNS Server you ISP provides to you and use them as forwarders.
Alternative, if your router supports this, you can use the Router IP as DNS Forwarder.

That's what I'll do when I get home, is use the routers IP, I think that would work. On the server, it's gateway/router entry is set to the routers IP, so it would work.

If not, I'll be replying later

Ok, good luck