Let’s get started by installing our Primary DNS server, ns1. Here is a table with example names and IP addresses: Host Our Goalīy the end of this tutorial, we will have a primary DNS server, ns1, and optionally a secondary DNS server, ns2, which will serve as a backup.

If you utilize multiple datacenters, you can set up an internal DNS within each respective datacenter. 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. 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. Note: 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. Refer to the following table the relevant details: Host Therefore, host1’s private Fully-Qualified Domain Name (FQDN) will be “”. With these assumptions, we decide that it makes sense to use a naming scheme that uses “” to refer to our private subnet or zone. Both VPS are somehow related to our web application that runs on “”.Both VPS have private networking enabled (and are on the 10.128.0.0/16 subnet).We have two existing VPS called “host1” and “host2”.Example Hostsįor example purposes, we will assume the following: If you are unfamiliar with DNS concepts, it is recommended that you read at least the first three parts of our Introduction to Managing DNS. Root access to all of the above ( steps 1-4 here).Optional: A new VPS to serve as a Secondary DNS server, ns2.

A new VPS to serve as the Primary DNS server, ns1.

Some servers that are running in the same datacenter and have private networking enabled.

To complete this tutorial, you will need the following: The CentOS version of this tutorial can be found here.

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. In this tutorial, we will go over how to set up an internal DNS server, using the BIND name server software (BIND9) on Ubuntu 14.04, that can be used by your Virtual Private Servers (VPS) to resolve private host names and private IP addresses. Setting up your own DNS for your private network is a great way to improve the management of your servers. Using fully qualified domain names (FQDNs), instead of IP addresses, to specify network addresses eases the configuration of services and applications, and increases the maintainability of configuration files. 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).

Cara setting dns windows 10