In
CannonR1 said:
I'm confussed, We have a registered Domain name for the
company, say company.co.uk
If you want to make your AD name the same as your external name, that is
fine.
what should the internal DC be
called? I called it company.co.uk but get wrong host name
errors and no dns server found.
The domain name, as you stated, apparently is company.co.uk. That's the
domain name. Now you need a host name, such as DC1 or DC or whatever. Then
the FQDN of the machine will be:
dc1.company.co.uk.
Should it be DC1.company.
co.uk or what?
Yep.
Our ISP hosts our web site and is the
primary DNS with no dynamic updating,
You can't use their DNS for AD. Need to use your own internal one. You can
setup DNS on your own domain controller. Do not use the ISP's or numerous
errors will result. If you want efficient Internet resolution, use a
Forwarder. If the forwarding option is grayed out, delete the Root zone.
This shows how to do both:
http://suport.microsoft.com/?id=300202
Keep in mind, using the same internal/external name (called split horizon)
requires additional administrative procedures on your part, such as not
being able to get to your external website by
www.company.uk.co since that
record does not exist on your internal DNS (since you need to point only to
your internal DNS for AD to work correctly). And since the names are the
same, DNS will not forward out name requests for a name that it knows
itauthorative for (meaning that the zone is on that machine). Now if you
want your users to get to your website by
http://company.co.uk, that's a
couple registry chantges to make that work. See what I mean?
Since not being well versed in DNS or AD, I would probably suggest to use a
different internal name, such as:
company.internal
company.co.corp
company.net
company.corp
etc
This way you will not be over burdened with the methods and registry
alterations to make it work properly.
Just need to get
private internal network up and running ie AD & DC with
internal DNS. Only got 4 servers and 12 pc's cant be that
difficult.
Actually it's not that difficult. Did you read up on the documentation at
Microsoft's site or attend any classes? It's really very easy.
Not to deluge you with reading, but here are some pertinent links that will
help you out.
DNS and AD FAQ:
http://suport.microsoft.com/?id=291382
237675 Setting Up the Domain Name System for Active Directory :
http://suport.microsoft.com/?id=237675
254680 DNS Namespace Planning :
http://suport.microsoft.com/?id=254680
AD and DNS Planning Guide:
http://www.microsoft.com/technet/tr...windows2000/deploy/adguide/adplan/default.asp
Configure DNS for AD:
http://www.microsoft.com/windows2000/en/server/help/sag_DNS_pro_ConfigServerForDS.htm
DNS Requirements for Deploying Active Directory:
http://www.microsoft.com/technet/tr...prodtechnol/windows2000serv/deploy/dnsreq.asp
DNS Requirements for Deploying Active Directory in Windows 2000:
http://www.microsoft.com/technet/tr...ol/ad/windows2000/deploy/prodspecs/dnsreq.asp
Chapter 4 - Active Directory Design:
http://www.microsoft.com/technet/tr...change/exchange2000/reskit/part2/c04names.asp
Any help appriciated
CannonR1
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
