You need to name the Active Directory domain valid in your network. Name must be unique in your local network.
At tis stage, you don’t have a specific Internet public Domain, you can use “.local” as a Top level domain root name.
At this case, if my Active Directory name is “AVALON”, it will be “avalon.local”.
Example, I would like to make our Active Domain cool and easy to type because the user very often type that name when the User Account name is identified in Authentication pop-up and etc. Bad: computerassociatecorp Good: whitedwarf , avalon Also, consider Domain name (former Windows NT Domain) as a NetBIOS name is upper case name. – WHITEDWARF, AVALON
Domain Name – Part of Organization Public DNS Domain
With regard to your internet access network, if your Active Directory domain is supposed to be a part of your own Internet valid public domain name, consider having the Active Directory domain as a sub domain of your primary internet domain.
Example, I have “toshitoshi.net” as the internet domain. I would like to get my Active Directory as a part of its internet domain name space.
so, in this case, I’m going to create my Active Directory domain as a part of it. The FQDN of my Active Directory will be “avalon.toshitoshi.net”.
DNS server structure (Name Lookup Query fowarders) needs to be designed properly.
If you have your DNS Server or DNS hub server in your network, make sure you can use that DNS server from Active Directory DNS server as name query forwarder target.
New our Active Directory will have own DNS server to store all DNS Host record and reverse lookup record to find the Domain member node by node name within TCP/IP network.
All your client/server in your Active Directory including the Platform Servers (AD server is a part of it) will point Active Directory DNS server as the primary DNS server. Your parent DNS server may help your Active Directory members to reach to node placed into your same network.
DHCP? Static IP?
How is your IP network managed for assigning the IP address to the Server/Client node?
If your network is new, consider using the DHCP server integrated into Active Directory to make IP network manageable easily.
If you have the DHCP or IP address managed statically, it is ok. Please continue.
If you are using the separate DHCP server system in your network, it will lease the IP address to your Active Directory Client and Servers. The leased IP will be reported to the DNS server with the node name and DNS server store it into the DNS name space.
But, AD server must be configured with Static IP address. Please make sure your DHCP server exclude that IP address from the lease range so that AD server IP address can be avoided from getting leased to other machine.
IP Network to be validated.
Make sure you know your P network information well such as Default Gateway IP address, Parent DNS server, IP Segment subnet mask.
Later, you may create separate IP Network for the specific purpose such as Storage Area network in iSCSI. You must make sure that the IP segment will never conflict with later new IP segment.
In the IP segment subnet design, make sure the node count you are going to store into the network is sufficient. 24bit mask (255.255.255.0) can have only 253 nodes inside. Consider using 23bit mask (255.255.254.0) or so.
Simplest Summary Local Domain in private network
Active Directory Domain (NetBIOS name/NT Domain) : GOGGLE
Active Directory FQDN: goggle.local
DNS Server: Active Directory integrated
IP Segment: 192.168.2.1/24
Net Mask: 255.255.255.0
Default gateway: 192.168.2.1
DNS forwarder: 192.168.200.5
DHCP Server: Active Directory integrated / Lease range 192.168.2.50-100
1st AD Server: KSWAD001(KSWAD001.goggle.local) / 192.168.2.10
Ok, you are ready to build the AD Server and your Active Directory.
Set up the AD Computer- We use Windows Server 2022 GUI installation.
Enable Active Directory Service and DNS (+DHCP if you need).
