> Read inline please.
>
> In news:%23qY8ayouHHA.3640[ at ]TK2MSFTNGP05.phx.gbl,
> Mike Sharp <rdcpro[ at ]hotmail.com> typed:
> <snip>
>
>> Most of the books I've read are concerned more with this scenario
>> where there is an internal corporate network, and don't explicitly
>> cover my needs, which is more of an ISP scenario.
>>
>
> *************
>> All the customers will need AD accounts either in my domain
>> (organized by OU, I suppose), or in child domains of my domain.
>
> Why do you say this?
> Local accounts will be just as well unless you are providing a service to
> them that requires Active Directory, like Exchange, I haven't seen
> anything
> in this post about having an Exchange server, and SQL and WSS doesn't need
> a
> domain.
>
> ************
>> I believe, from what I've read, that I should use an empty root domain
>> (coolwsshosting.com). But if I do that, how will people who browse to
>> coolwsshosting.com find my site, which is on the WFE, not the DC?
>
> Your internal Domain can be any DNS compatible domain name, it does not
> have
> to be in a public TLD, it could be coolwsshosting.mike if you want, the
> name
> won't be used by internet users anyway.
>
> ************
>> Isn't there supposed to be a host record for the domain, and if so,
>> how does that work?
>
> From the internet, it doesn't matter, internet users won't see the
> internal
> name, internally the AD Domain name must resolve to all Domain Controller
> IP
> addresses that have file sharing enabled.
>
> ************
>> But the main questions are:
>> 1. How do I set up DNS with GoDaddy so that my local domain
>> controller can function as I need it?
>
> When you set up DNS at GoDaddy you don't need to consider you Domain
> Controller as a part of it. Your DC will not need to see the Public DNS
> Servers at GoDaddy. You have to think of the Public Domain and your
> internal
> AD Domain as two totally separate entities, with the same name.
> The Public users won't get to see the internal DNS server at all, and
> shouldn't. The internal DNS is for internal machines and users locating
> and
> Authenticating with the Domain Controller.
> The GoDaddy Servers need records with public (routable) IPs for locating
> web
> sites, ftp sites, mail servers and other internet related services only.
> Users on the internet will not and should not be Authenticating with
> Active
> Directory, allowing access to the AD services are all done internally.
>
> **************
>> 2. How do I set up my DC AD and DNS?
>
> The DC should be running its own DNS with AD Integrated zones that allow
> only secure updates, the DC will use its own address for DNS, and the Web
> server will also be using the DC for DNS for its own internal resolution.
> Unless this web server is hosting an Exchange Server (Don't recall if the
> web edition can even run Exchange anyway) it shouldn't be a member of the
> domain. Any Authentication done in WSS is done with local accounts.
>
> ****************
>> 3. How do I set up the DNS entries on the NICs so everybody is happy,
>> and talking over the right network cards?
>
> All internal name resolution must be done to internal IP addresses, so the
> internal servers(machines) will point only to internal DNS servers, which
> need to have zones for each domain, but its records have internal IP
> addresses. It doesn't matter how small you network is, even if it has only
> one or two machines internal name resolution needs to be to local IP
> addresses so the internal machines can communicate unrestricted without
> going through a firewall.
>
>
> ****************
>> GoDaddy allows SRV records with the following fields:
>
> Unless you are providing a service to internet users that uses SRV
> records,
> like some Instant Messaging services use, you don't need to create any
> public SRV records. Other applications like web browsers do not query for
> or
> see SRV records. You certainly don't want to create any SRV records for
> your
> DC on the internet DNS, you would basically have to open your firewall
> wide
> open, and hackers would have a field day.
>
> The only records that you will be concern with are A, CNAME, MX and TXT RR
> Types. You may possibly some day need AAAA (IPv6) RR types. At this point
> in
> time, I'd say most routers on the internet don't support IPv6 anyway.
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
>
http://www.lonestaramerica.com/>
http://support.wftx.us/>
http://message.wftx.us/> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
>
http://home.in.tum.de/~jain/software/oe-quotefix/> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
>
http://www.oehelp.com/OEBackup/Default.aspx> ===================================
>
>