The Nameserver List Now that your resolver knows
The Nameserver List Now that your resolver knows which domains to try by default, you can tell it which nameservers to use. List each nameserver on a single line, in the order of preference. The nameservers will be tried in order. It would look something like this: ………………………………………………………………………………….. nameserver 127.0.0.1 nameserver 209.168.70.3 nameserver 192.168.87.3 ………………………………………………………………………………….. Note that the first entry in this list is the “loopback” IP address 127.0.0.1. You’ll need this entry if the machine is a nameserver because it tells the resolver to check the local host’s nameserver. While in some rare instances you might not want to use the local nameserver, you don’t have to, but in most cases it’s a waste of network bandwidth not to. With nameserver entries and either domain or search keywords, your /etc/resolv.conf is complete. DNS Information Sources To truly manage Internet services, you must be able to control your own domain naming service. While many ISPs will provide this service for you, you don’t want to have to coordinate with their staff to make a vital change in your infrastructure. Now that you know how to look at DNS data, and how the chain of DNS authority works, you can start building your own nameserver. FreeBSD includes all the software you need to run a DNS server; all you have to do is configure it and turn it on. We’ll do so by building the two possible sources of hostname and IP address information: the hosts file and the named daemon. Each is configured separately. The Hosts File The /etc/hosts file matches Internet addresses to hostnames for a single host. However, while the hosts file is very simple, its contents are only effective on a single machine. One system cannot use the hosts file from another system, without some unpleasant tricks. Dynamic nameserver programs have largely superseded /etc/hosts, but the hosts file is still useful on small networks or behind a Network Address Translation (NAT) device. For example, the hosts file is just fine if you have one or two servers and if someone else is responsible for managing your public nameservice. If you have multiple servers that would each have to be maintained separately, you should investigate using a full-fledged nameserver. Each line in /etc/hosts represents one host. The first entry on each line is an IP address, and the second is the fully qualified domain name of the host, such as mail.mycompany.com. Following these two entries you can list an arbitrary number of aliases for that host. For example, a small company might have a single server that handles mail, FTP, Web services, DNS, and a variety of other functions. A desktop on that network might have a hosts entry 275
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Cheap Web Hosting services