It is helpful for you to familiarize yourself first with the different types of DNS servers before deciding on which DNS configuration to adopt.

It is possible to utilize the DNS servers provided by your Internet Service Providers (ISPs) for your website and internet browsing. However, if you can make efforts to configure your own DNS servers, there are some benefits to derive from doing so. Here, you will learn how to configure Bind9 DNS server, an open source software, as an Authoritative-only DNS server.
You will need, at least, two servers: One for the “Master” Server, and the other for the “Slave” Server. As explained above, most zone files originate from the Master Server and are transferred to the Slave Server.

Purpose	DNS FQDN	IP Address
Master name server	ns1.goodfoods.com.	183.0.2.4
Slave name server	ns2.goodfoods.com.	183.0.2.5
Web server	www.goodfoods.com.	183.0.2.6

Both the Master and Slave DNS Servers will be configured so that they can perform effectively.

• First, make sure that the hostname on the Name Servers is properly set or configured on both the Master and Slaver Servers
• Install Bind on both Master and Slave Servers—the Bind software already exists within the Ubuntu’s repositories, and what should be done is to just update the local setting
• To fully configure the Master Server, the following processes must be carefully carried: The configuration of the Options File; configuring the Local File; in case your ISP does not have Reverse Zones, you can configure that, too; setting up the Forward Zone File; finally, testing the files and restarting the service

Setting up the Slave DNS Server will be easier than configuring the Master DNS Server.

• First, configure the Options File
• Configure the Local Configuration File
• The Forward Zone is also configured so that the Files that could be transferred from the Master DNS Servers are properly configured. This makes it easy or efficient for specified files to be transferred to the Slave DNS Server
• Make sure you test the files and restart the service

The configuration of your Authority-only name servers would have been completed after successfully carrying out the two configurations described above. However, you must delegate the authority for your domain to the name servers. To do this, you would need to sign in into the control panel of the company that sold the domain to you. Your registry will not automatically delegate the authority to the NS records; so, you will need to create a glue record. A glue record is an “A” record that specifies the IP addresses for the name servers after it has successfully specified the name servers that it is delegating authority to.
All you need to do is to just list the name servers that will manage the authority of the domain. However, if the name servers are located within the domain itself, you will need to create an “A” record for the name servers in the parent zones. You must make sure that the delegation is properly aligned, or else the DNS resolvers will become stuck in the loop, having failed to locate the IP addresses of the domain name servers.