Debian Based Local Network Domain Name System Cache Server

Read More About Business Network Mkt

A Domain name system server is piece of software program that runs on a pc, designed to translate a domain name into the true ip address. In other words whenever you kind an internet address into your web browser, your web provider's Domain name system server will look into it records and seek for the domain identify that your are requesting. The main reason you'd need a local dns cache server is to lower the ping charge when you request a selected internet page. Another excuse to have a local dns cache server is because the dns data will be tailored to your use.

Once you request a specific internet tackle or area in your web browser, one of two issues will occur on the internet providers DNS server. The very first thing that might happen while you request a site is that the handle is already located inside the internet suppliers dns records.

The second thing that might occur when you request an internet tackle is that domain isn't located within your internet suppliers records. If the area that you're requesting will not be along with your internet suppliers Domain name system server, then the tackle will have to be found at a special dns server, then will be added to your web providers dns server records.

If you are already utilizing a linux os such as Ubuntu, simply open up your terminal program and type in dig net-address.com. For example I used Yahoo, so I typed in dig yahoo.com. As you can see from the picture beneath that my ping fee took 30 milliseconds for my request to succeed in the dns server. For the specialists out there, additionally, you will notice that I am already utilizing a local dns server.

Now upon getting run the dig command once, rerun same command again to see what you'll get. Once I ran dig yahoo.com once more you will now discover that my ping charge to my dns server is only one millisecond. Now you may assume saving solely 29 milliseconds doing one search, but in the event you add this time up over many searches, it pays itself off. For those out there that still use dial up or satellite tv for pc internet will acquire essentially the most profit by having their very own local DNS server. For instance a satellite tv for pc internet provider equivalent to Wild Blue or Hughes Net might need wherever from a 200 msec - 1500 msec ping time, so when you may cut this time down to a few milliseconds would find yourself saving quite a lot of time.

Now it's time to get all the way down to the center of setting up your very own local dns server. On this tutorial I shall be exhibiting you how setup your local dns cache server on one computer, but you could set your dns server to regulate your entire local network. This might enable every pc on your community to talk to the local dns server, saving time for everybody on the local network. When you have a number of computer systems on you community and want to setup a local community dns server, comply with the Ubuntu gateway firewall tutorial, then come back to this page to setup you local dns server. Just just remember to install dnsmasq as a substitute of bind9.

The first that you'll want to do in establishing your local dns cache server is to install the dns server software.

sudo apt-get install dnsmasq vim

As soon as dnsmasq is installed, you'll now must configure the dnsmasq to act as a cache server.

vi /etc/dnsmasq.conf

Within 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 thing that you will need to do is edit the /and so forth/resolv.conf file to allow your local dns to have the ability to speak to your internet suppliers dns server, simply in case your local dns server would not comprise the online addresses your are trying for. If you first setup your local dns cache server, there won't be addresses in your dns server, so your dns server will want to have the ability to discover this deal with somewhere.

You internet providers dns tackle may be found utilizing many different methods, so I will explain just some of these ways. In case you are are utilizing a router strive typing one of these addresses to entry your default gateway. Open an online browser and type in 192.168.1.1 or 192.168.1.254 within the handle bar. In case you are using a 2wire gateway the address might be 192.168.1.254, and in case you are using one other router corresponding to a Linksys router, the tackle shall be 192.168.1.1.

In case you are on a Windows based laptop, simply open up the command immediate by going to Begin --> Accesories --> Command Prompt, or search for "cmd". After you have the command prompt open, sort 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 too can 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 you add 127.0.0.1 to the file, since this will tell the resolv.conf file to look at you local host first for the dns translation. As you may 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'm running a local dns server on my complete community, I have additionally added the address of my dns server. In all actuality 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 DNS
nameserver 10.0.0.1 <-----Local Network Gateway/DNS
nameserver 192.168.1.254 <-----Internet Providers DNS/Gateway

After you've gotten edited the /etc/resolv.conf file, you'll need to edit another file. The final file that it's worthwhile to edit is the /etc/dhcp3/dhclient.conf file.

vi /etc/dhcp3/dhclient.conf

All it's important to do is uncomment the road that claims prepend domain-name-servers 127.0.0.1.

prepend domain-name-servers 127.0.0.1

After you will have edited the /etc/dhcp3/dhclient.conf file, the very last thing that you will want to do is restart dnsmasq to use the new changes.

/etc/init.d/dnsmasq restart

Article Source: http://depositarticles.com/

Debian Based Local Domain Name System Cache Server Debian Based Internet Gateway and Router

Please Rate this Article

Not yet Rated

Click the XML Icon Above to Receive Business Network Mkt Articles Via RSS!

Additional Articles From - Home | Business | Business Network Mkt

Our other websites
All about SEO
Beauty Tips Forum

	Print This Article
	Post Comment
	Add To Favorites
	Email to Friends
	Ezine Ready

Submit Articles
Member Login
Link Us
Submission Guidelines
Ezine Notifications
Article RSS Feeds
Sitemap

New Stuff
About Us
Developer
Good shopping portal
Link to Us
Contact Us
Privacy Policy
Terms of Service