You should be able to easily adapt this setup to your own environment by replacing the host names and private IP addresses with your own.It is not necessary to use the region name of the datacenter in your naming scheme, but we use it here to denote that these hosts belong to a particular datacenter’s private network.
This is where we will define a list of clients that we will allow recursive DNS queries from (i.e.
your servers that are in the same datacenter as ns1).
This provides a central way to manage your internal hostnames and private IP addresses, which is indispensable when your environment expands to more than a few hosts.
The Cent OS version of this tutorial can be found here.
Let’s get started by installing our Primary DNS server, ns1. It will often be used to denote something that needs to be replaced with your own settings or that it should be modified or added to a configuration file.
For example, if you see something like ACL (access control list) block called “trusted”.
Therefore, host1’s private Fully-Qualified Domain Name (FQDN) will be host1.nyc3.
Refer to the following table the relevant details: Your existing setup will be different, but the example names and IP addresses will be used to demonstrate how to configure a DNS server to provide a functioning internal DNS.
According to our local configuration, that location should be $TTL 604800 @ IN SOA localhost. ( 2 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS localhost.
; delete this line @ IN A 127.0.0.1 ; delete this line @ IN AAAA ::1 ; delete this line First, you will want to edit the SOA record.
Setting up your own DNS for your private network is a great way to improve the management of your servers.