Dns config file debian

Learn more. How to setup DNS manually on Linux? Ask Question. Asked 3 years ago. Active 1 year, 8 months ago.

Viewed 31k times. How to properly setup the DNS? Improve this question. Add a comment. Retry : if an error occurs during the last refresh, it will be repeated at the end of time Retry. Expires ': the server is considered unavailable after the time expires. Many can be defined. Thus, it is possible to give them a priority, assigning a number. The lower the number, the higher the priority. The classes in the association determines the Internet class. Other classes are available CH and HS.

Bind Chroot Debian Wheezy and earlier The named daemon is started using the bind user by default. Starting bind as a non root user is good practice but to run the daemon in a chroot environment we also need specify the chroot directory. Update the symlink to the unit file with:- systemctl reenable bind9 Also advised to run: systemctl daemon-reload for systemd default systems, to pick up any changes to systemd configuration files. Thus, to set our DNS server to different clients, it is necessary to add the DHCP configuration file the following two lines: option domain-name "example.

Here is an example for a domain file for yourdomain. Please note this is a very generic example and there are more features to it. Please refer to the BIND documentation for help with these features. Any line starting with a ; is a comment line and is ignored by BIND. The first 6 lines are configuration lines for the zone. These lines tell it what the zone is yourdomain. These other things include a serial number used for keeping track of when it's updated, how often to refresh the database, how often to retry a zone transfer, when the zone information will expire and a default time to live.

If you do not do this, prolems can occur, especially if you are a primary server supplying information to secondary sites. Most of this information is only used if you have both master and slave systems.

The next two lines tell it who the primary DNS server is and who should get the mail for this domain. You can have multiple listings of each of these. To add more dns servers just repeat exactly what is listed changing the dns.

To add another mail server you do the same thing except you have an extra field. The "10" in the MX line states a priority, lower number being first. What this means is if you have 2 MX listings, one is 10 and one is 20, it will try to deliver the mail to the MX listing with the 10 priority and if it fails it will then go to the MX listing with the 20 priority. The rest of the zone file lists all your hosts and ips. For more information other features and configuration of this information check the BIND documentation.

The reverse lookup files are almost identical to the domain files with only minor changes. Here is an example of a reverse lookup file. The first section of this file is exactly the same as the first section of the domain zone files.

The bottom section is where it is different. This time we are listing the last part of the IP address first and then the hostname last. There are 2 things you must notice here. You have to use the fully qualified domain name here and you must put a ". These 2 things are important to the file and weird things will happen if you don't do it this way.

It can be either a standalone system or other servers Secondary can work off of it by performing zone transfers. A zone transfer is just that, transfering of zone files from one system to another. This is how a Primary server distributes it's zone information to other servers. I'll go through creating a fake domain and configuring BIND to work with that domain.

What we are going to do here is create a new domain. For our purposes we will use foo. In this section, we will setup your Debian system to be a Primary server for foo. To give you a better understanding on how all this works, I'll use the following servers with their corresponding IP's for the examples.

Using these for our example, dns. If you receive unexpected values, be sure to review the zone files on your primary DNS server e. Your internal DNS servers are now set up properly!

Now we will cover maintaining your zone records. Now that you have a working internal DNS, you need to maintain your DNS records so they accurately reflect your server environment.

Whenever you add a host to your environment in the same datacenter , you will want to add it to DNS. Here is a list of steps that you need to take:. If you remove a host from your environment or want to just take it out of DNS, just remove all the things that were added when you added the server to DNS i.

This makes configuration of services and applications easier because you no longer have to remember the private IP addresses, and the files will be easier to read and understand. Also, now you can change your configurations to point to a new servers in a single place, your primary DNS server, instead of having to edit a variety of distributed configuration files, which eases maintenance. Once you have your internal DNS set up, and your configuration files are using private FQDNs to specify network connections, it is critical that your DNS servers are properly maintained.

If they both become unavailable, your services and applications that rely on them will cease to function properly. This is why it is recommended to set up your DNS with at least one secondary server, and to maintain working backups of all of them. Where would you like to share this to? Twitter Reddit Hacker News Facebook.

Share link Tutorial share link. Sign Up. DigitalOcean home. Community Control Panel. Hacktoberfest Contribute to Open Source. By Justin Ellingwood Published on September 6, Not using Debian 9? Choose a different version or distribution. Debian 9. Introduction An important part of managing server configuration and infrastructure includes maintaining an easy way to look up network interfaces and IP addresses by name, by setting up a proper Domain Name System DNS.

Prerequisites To complete this tutorial, you will need the following infrastructure. Create each server in the same datacenter with private networking enabled : A fresh Debian 9 server to serve as the Primary DNS server, ns1 Recommended A second Debian 9 server to serve as a Secondary DNS server, ns2 Additional servers in the same datacenter that will be using your DNS servers On each of these servers, configure administrative access via a sudo user and a firewall by following our Debian 9 initial server setup guide.

Example Infrastructure and Goals For the purposes of this article, we will assume the following: We have two servers which will be designated as our DNS name servers. We will refer to these as ns1 and ns2 in this guide. We have two additional client servers that will be using the DNS infrastructure we create. We will call these host1 and host2 in this guide. All of these servers exist in the same datacenter. We will assume that this is the nyc3 datacenter.

All of these servers have private networking enabled and are on the