Active Directory Domain Services (AD DS) uses Domain Name System (DNS) name resolution services to make it possible for clients to locate domain controllers and for the domain controllers that host the directory service to communicate with each other. Please see how to add and verify a custom domain name to Azure Active Directory, Active Directory: How to Setup a Domain Controller, how to locate and edit the host file on macOS, and how to know when an IP or domain has been blacklisted.
AD DS enables easy integration of the Active Directory namespace into an existing DNS namespace. Features such as Active Directory-integrated DNS zones make it easier for you to deploy DNS by eliminating the need to set up secondary zones, and then configure zone transfers..
Kindly refer to the following related guides: How to setup a cache-only DNS server, how to locate and edit the hosts file on Windows, and how to install RSAT tools: DNS manager console missing from RSAT tools on Windows 10, how to setup SPF and TXT Records in AWS,
Launching DNS Manager for A Record Addition
To add an A record, kindly launch the DNS snap-in as shown below. From the Server Manager, click on Tools and then select Server Manager. Alternatively, you could start the DNS Manager from the Administrative Tools as well “(Click on Start, – Programs – Administrative Tools – DNS Manager).
In the console tree, right-click the applicable forward lookup zone, and then click New Host (A or AAAA) as shown below. See this guide for the different types of DNS Records you can create.
In the New Host window, enter the Name (e.g, TechDACluster), followed by the IP Address as shown below.
- Ensure you check the “Create Associated PTR record” if you’ve configured the Reverse Arpa zone for automatic PTR record addition.
- Click “Add Host” when you’ve finished.
As shown below, we successfully created the record.
Find troubleshooting insights in these guides. The following error occurred when DNS was queried for the service location (SRV): Error code 0x0000232B RCODE_NAME_ERROR, and the following errors occurred attempting to join the domain: The specified domain either does not exist or could not be contacted.
I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.
these steps are well known and all over the internet. However after searching for hrs I wasnt able to find the next natural step: that is pinging new host by name by client PCs in AD. After I registering my LINUX in AD it is pingable by name only on domain controller but not by any other PC in the zone (I can ping new host by IP though from any machine).
Did you actually try to add a LINUX host and making sure is pingable by name from other PCs?
No, I haven’t had the need to test this. But in the future, we will be writing a guide on why join a Linux device to AD and how to join a Linux device to AD.
thank you Christian for the replay. Instr. for joining Linux to AD are out there too (like realm or sssd, etc) but I will definitely check your upcoming guide.