DNS and ActiveDirectory

I have 2 windows 2008 standard boxes.
I have one to handle AD and the other to handle several hosted
websites (public facing).
The problem I'm running into is that the AD box apparently has to run
DNS, and my web server is as well, and unless I tell my DHCP router to
use the AD server as the DNS, client computers can't join the domain.
Am I missing something?

Also, when setting up a new domain, can you specify a non-internet
based domain name? ie: mycompany.local instead of local.mycompany.com?
I've seen it before, and tried it, but for some reason I kept getting
DNS errors.

Any help would be appreciated.

How do you setup the DNS. Post the results of ipconfig /all and nslookup
here may help.

Yes, you can use domain.local.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
<(E-Mail Removed)> wrote in message
news:33a6df5d-91fd-4e49-8eb4-(E-Mail Removed)...
>I have 2 windows 2008 standard boxes.
> I have one to handle AD and the other to handle several hosted
> websites (public facing).
> The problem I'm running into is that the AD box apparently has to run
> DNS, and my web server is as well, and unless I tell my DHCP router to
> use the AD server as the DNS, client computers can't join the domain.
> Am I missing something?
>
> Also, when setting up a new domain, can you specify a non-internet
> based domain name? ie: mycompany.local instead of local.mycompany.com?
> I've seen it before, and tried it, but for some reason I kept getting
> DNS errors.
>
> Any help would be appreciated.

<(E-Mail Removed)> wrote in message
news:33a6df5d-91fd-4e49-8eb4-(E-Mail Removed)...
> I have 2 windows 2008 standard boxes.
> I have one to handle AD and the other to handle several hosted
> websites (public facing).
> The problem I'm running into is that the AD box apparently has to run
> DNS, and my web server is as well, and unless I tell my DHCP router to
> use the AD server as the DNS, client computers can't join the domain.
> Am I missing something?
>
> Also, when setting up a new domain, can you specify a non-internet
> based domain name? ie: mycompany.local instead of local.mycompany.com?
> I've seen it before, and tried it, but for some reason I kept getting
> DNS errors.
>
> Any help would be appreciated.

Yes, that is the way AD works. If you are running AD behind an ADSL
router, you need to turn off its DHCP function and run your own DHCP on the
server. (This should hand out the router IP as the gateway but the DC's IP
address for DNS). For AD to work properly, the clients must use the local
DNS. That is how they find the AD resources. They cannot use the DNS relay
provided by the router.

To let your client machines access public sites, set your local DNS to
forward to a public DNS.

What you call your local domain is entirely up to you. It does not
have to be the same as your registered Internet name. Your local machines
use the local name and the local DNS. Outside users accessing your website
use your public name.

Hello (E-Mail Removed),

Let the router do it's basic job, routing, disable DHCP service on it. The
DC should handle DNS and DHCP.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I have 2 windows 2008 standard boxes.
> I have one to handle AD and the other to handle several hosted
> websites (public facing).
> The problem I'm running into is that the AD box apparently has to run
> DNS, and my web server is as well, and unless I tell my DHCP router to
> use the AD server as the DNS, client computers can't join the domain.
> Am I missing something?
> Also, when setting up a new domain, can you specify a non-internet
> based domain name? ie: mycompany.local instead of local.mycompany.com?
> I've seen it before, and tried it, but for some reason I kept getting
> DNS errors.
>
> Any help would be appreciated.
>