A DNS server is piece of software program that runs on a pc, that will translate a website name into the true ip address. In different words if you sort an online address into your internet browser, your internet provider's DNS server will look into it data and seek for the domain name that your are requesting. The main purpose you'd want a local dns cache server is to decrease the ping rate whenever you request a specific net page. One more reason to have a local dns cache server is as a result of the dns records can be tailor-made to your use. When you request a particular web tackle or area in your web browser, one of two things will happen on the web suppliers DNS server. The first thing that would happen while you request a site is that the address is already situated inside the web providers dns records. The second thing that could occur while you request a web address is that domain isn't situated inside your web providers records. If the domain that you are requesting isn't with your internet providers DNS server, then the handle should be discovered at a special dns server, then can be added to your web suppliers dns server records. If you're already using a linux os reminiscent of Ubuntu, merely open up your terminal program and sort in dig web-address.com. For instance I used Yahoo, so I typed in dig yahoo.com. As you possibly can see from the image beneath that my ping charge took 30 milliseconds for my request to reach the dns server. For the consultants on the market, you will also notice that I am already using a local dns server. Now once you have run the dig command once, rerun same command once more to see what you'll get. As soon as I ran dig yahoo.com once more you will now notice that my ping charge to my dns server is only one millisecond. Now chances are you'll suppose saving solely 29 milliseconds doing one search, but in case you add this time up over many searches, it pays itself off. For those on the market that also use dial up or satellite tv for pc internet will achieve probably the most profit by having their very own local DNS server. For example a satellite internet supplier corresponding to Wild Blue or Hughes Web may need wherever from a 200 msec - 1500 msec ping time, so in case you may reduce this time down to a couple milliseconds would find yourself saving a variety of time. Now it's time to get all the way down to the guts of organising your very own local dns server. On this tutorial I will likely be showing you how setup your local dns cache server on one computer, however you might set your dns server to control your entire local network. This is able to permit each pc on your network to speak to the local dns server, saving time for everybody on the local network. When you have multiple computer systems on you community and would like to setup a local community dns server, follow the Ubuntu gateway firewall tutorial, then come back to this page to setup you local dns server. Just just be sure you set up dnsmasq as an alternative of bind9. The first that you'll want to do in establishing your local dns cache server is to put in the dns server software. sudo apt-get install dnsmasq vim As soon as dnsmasq is installed, you will now need to configure the dnsmasq to behave as a cache server. vi /etc/dnsmasq.conf Throughout the dnsmasq.conf file look for the line that says listen-address=127.0.0.1 and take away the to make this line active. listen-address=127.0.0.1 The subsequent factor that you will want to do is edit the /etc/resolv.conf file to allow your local dns to have the ability to speak to your web providers dns server, just in case your local dns server does not comprise the web addresses your are looking for. Once you first setup your local dns cache server, there is not going to be addresses in your dns server, so your dns server will need to have the ability to find this address somewhere. You web providers dns deal with can be found using many alternative methods, so I'll explain only a few of these ways. If you are are utilizing a router attempt typing certainly one of these addresses to access your default gateway. Open an online browser and type in 192.168.1.1 or 192.168.1.254 in the deal with bar. If you are using a 2wire gateway the handle will probably be 192.168.1.254, and in case you are using one other router such as a Linksys router, the handle will be 192.168.1.1. If you are on a Home windows primarily based computer, simply open up the command prompt by going to Begin --> Accesories --> Command Prompt, or search for "cmd". Once you have the command immediate open, type in ipconfig /all. Once you have typed the ipconfig /all command simply look although the list for DNS servers. In case you still do not know what the hell I am speaking about you can also use the deal with of your default gateway or the dns addresses supplied by OpenDNS.com. 208.67.222.222 and 208.67.220.220. Now it is time to edit the /etc/resolv.conf file. vi /etc/resolv.conf Be sure to add 127.0.0.1 to the file, since this will tell the resolv.conf file to take a look at you local host first for the dns translation. As you possibly can see from my resolv.conf file that I've added 127.0.0.1, 10.0.0.1 and 192.168.1.254. Since I am operating a local dns server on my whole network, I've additionally added the tackle of my dns server. In all reality 127.0.0.1 and 10.0.0.1 addresses are referring to the same computer. domain gateway.2wire.net search gateway.2wire.net nameserver 127.0.0.1 <-----Localhost DNS nameserver 10.0.0.1 <-----Local Network Gateway/Domain name system nameserver 192.168.1.254 <-----Internet Providers Domain name system/Gateway After you've edited the /etc/resolv.conf file, you will need to edit yet one more file. The last file that that you must edit is the /etc/dhcp3/dhclient.conf file. vi /etc/dhcp3/dhclient.conf All you must do is uncomment the line that claims prepend domain-name-servers 127.0.0.1. prepend domain-name-servers 127.0.0.1 After you may have edited the /etc/dhcp3/dhclient.conf file, the very last thing that you'll want to do is restart dnsmasq to use the brand new changes. /etc/init.d/dnsmasq restart
Article Source: http://www.articlecontentprovider.com/articlesubmit
A Domain name system server is piece of software program that runs on a computer, designed to translate a domain name into the true ip address. In other words whenever you sort an online address into your net browser, your web supplier's Domain name system server will look into it information and seek for the area name that your are requesting. The primary motive you'll desire a local dns cache server is to decrease the ping price if you request a particular web page. Another excuse to have ...
Linux Local Network Domain Name System Cache Server Ubuntu Internet Gateway and Router
Please Rate this Article
5 out of 5 4 out of 5 3 out of 5 2 out of 5 1 out of 5
