A DNS server is piece of software that runs on a pc, designed to translate a domain name into the true ip address. In other words while you type an internet address into your web browser, your web provider's Domain name system server will look into it data and seek for the area title that your are requesting. The main cause you'd want a local dns cache server is to lower the ping rate once you request a specific internet page. One more reason to have a local dns cache server is because the dns information will be tailored to your use. When you request a specific web address or area in your web browser, one of two issues will occur on the internet suppliers Domain name system server. The very first thing that could occur once you request a domain is that the tackle is already situated throughout the internet suppliers dns records. The second thing that might happen while you request a web handle is that domain just isn't positioned within your internet providers records. If the domain that you're requesting will not be together with your web providers DNS server, then the tackle must be found at a special dns server, then will likely be added to your web suppliers dns server records. If you are already using a linux os reminiscent of Ubuntu, merely open up your terminal program and type in dig net-address.com. For instance I used Yahoo, so I typed in dig yahoo.com. As you may see from the picture below that my ping rate took 30 milliseconds for my request to succeed in the dns server. For the consultants on the market, you will also realize that I'm already using a local dns server. Now once you have run the dig command once, rerun identical command again to see what you'll get. As soon as I ran dig yahoo.com again you will now discover that my ping charge to my dns server is only 1 millisecond. Now chances are you'll assume saving only 29 milliseconds doing one search, but in case you add this time up over many searches, it pays itself off. For those out there that also use dial up or satellite tv for pc internet will gain the most benefit by having their very own local Domain name system server. For example a satellite internet provider equivalent to Wild Blue or Hughes Web might need anywhere from a 200 msec - 1500 msec ping time, so for those who could lower this time down to a few milliseconds would end up saving a lot of time. Now it's time to get all the way down to the heart of setting up your very personal local dns server. In this tutorial I will probably be exhibiting you how setup your local dns cache server on one pc, however you would set your dns server to control your complete local network. This could allow every pc on your community to talk to the local dns server, saving time for everybody on the local network. If in case you have multiple computer systems on you network and wish to setup a local network dns server, comply with the Ubuntu gateway firewall tutorial, then come back to this web page to setup you local dns server. Just just remember to set up dnsmasq instead of bind9. The first that you will need to do in setting up your local dns cache server is to install the dns server software. sudo apt-get install dnsmasq vim Once dnsmasq is installed, you will now have to configure the dnsmasq to act as a cache server. vi /etc/dnsmasq.conf Within the dnsmasq.conf file search 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'll want to do is edit the /and so forth/resolv.conf file to permit your local dns to be able to discuss to your web suppliers dns server, simply in case your local dns server doesn't include the web addresses your are wanting for. If you first setup your local dns cache server, there won't be addresses in your dns server, so your dns server will need to have the ability to discover this tackle somewhere. You web providers dns handle may be discovered using many different techniques, so I'll clarify just some of those ways. In case you are are using a router strive typing one in all these addresses to entry your default gateway. Open an online browser and sort in 192.168.1.1 or 192.168.1.254 within the handle bar. If you are utilizing a 2wire gateway the handle shall be 192.168.1.254, and in case you are utilizing one other router resembling a Linksys router, the deal with will be 192.168.1.1. In case you are on a Windows based mostly computer, merely open up the command prompt by going to Begin --> Accesories --> Command Prompt, or search for "cmd". After getting the command immediate open, kind in ipconfig /all. Upon getting typed the ipconfig /all command simply look though the checklist for DNS servers. Should you still do not know what the hell I am talking about you can too use the address of your default gateway or the dns addresses provided by OpenDNS.com. 208.67.222.222 and 208.67.220.220. Now it's time to edit the /etc/resolv.conf file. vi /etc/resolv.conf Be sure to add 127.0.0.1 to the file, since it will inform the resolv.conf file to look at you local host first for the dns translation. As you can see from my resolv.conf file that I have added 127.0.0.1, 10.0.0.1 and 192.168.1.254. Since I am running a local dns server on my complete community, I have also added the deal with of my dns server. In all reality 127.0.0.1 and 10.0.0.1 addresses are referring to the identical computer. domain gateway.2wire.net search gateway.2wire.net nameserver 127.0.0.1 <-----Localhost Domain name system nameserver 10.0.0.1 <-----Local Network Gateway/Domain name system nameserver 192.168.1.254 <-----Internet Providers Domain name system/Gateway After you may have edited the /etc/resolv.conf file, you will have to edit yet another file. The last file that it's essential to edit is the /etc/dhcp3/dhclient.conf file. vi /etc/dhcp3/dhclient.conf All it's a must to do is uncomment the road that says prepend domain-name-servers 127.0.0.1. prepend domain-name-servers 127.0.0.1 After you've gotten edited the /etc/dhcp3/dhclient.conf file, the last thing that you will need to do is restart dnsmasq to apply the new changes. /etc/init.d/dnsmasq restart
Article Source: http://www.articlecontentprovider.com/articlesubmit
A DNS server is piece of software program that runs on a computer, that will translate a site name into the true ip address. In different words if you kind an online address into your internet browser, your internet supplier's DNS server will look into it data and search for the area name that your are requesting. The principle reason you'll desire a local dns cache server is to decrease the ping fee if you request a particular web page. One more reason to have a local dns cache server is as ...
Linux Local 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
