Linux Local Network DNS Cache Server

Read More About Business Network Mkt

A DNS server is piece of software that runs on a pc, designed to translate a website name into the true ip address. In other words if you kind a web address into your net browser, your web provider's Domain name system server will look into it information and search for the area identify that your are requesting. The principle motive you'd need a local dns cache server is to decrease the ping price when you request a particular net page. One more reason to have a local dns cache server is because the dns data shall be tailored to your use.

When you request a selected net handle or domain in your internet browser, one of two things will happen on the web providers DNS server. The very first thing that would occur whenever you request a site is that the deal with is already positioned inside the web suppliers dns records.

The second factor that could happen when you request an internet address is that domain is just not located within your internet providers records. If the domain that you're requesting isn't with your internet suppliers DNS server, then the handle should be discovered at a different dns server, then will probably be added to your internet suppliers dns server records.

If you're already using a linux os equivalent to Ubuntu, simply open up your terminal program and sort in dig internet-address.com. For example I used Yahoo, so I typed in dig yahoo.com. As you may see from the image under that my ping price took 30 milliseconds for my request to achieve the dns server. For the specialists on the market, you will also understand that I'm already using a local dns server.

Now after you have run the dig command once, rerun same command again to see what you will get. As soon as I ran dig yahoo.com once more you'll now notice that my ping rate to my dns server is only 1 millisecond. Now you may think saving solely 29 milliseconds doing one search, however 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 web will achieve essentially the most profit by having their own local Domain name system server. For instance a satellite web supplier comparable to Wild Blue or Hughes Net might have anywhere from a 200 msec - 1500 msec ping time, so should you could minimize this time down to a couple milliseconds would find yourself saving loads of time.

Now it is time to get all the way down to the heart of establishing your very personal local dns server. On this tutorial I will be exhibiting you how setup your local dns cache server on one laptop, but you could set your dns server to manage your entire local network. This is able to enable every 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 wish to setup a local network dns server, comply with the Ubuntu gateway firewall tutorial, then come again to this page to setup you local dns server. Just make sure that you install dnsmasq as a substitute of bind9.

The primary that you will want to do in establishing your local dns cache server is to put in the dns server software.

sudo apt-get install dnsmasq vim

Once dnsmasq is installed, you'll now must 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 remove the to make this line active.

listen-address=127.0.0.1

The next factor that you will want to do is edit the /etc/resolv.conf file to permit your local dns to be able to speak to your web suppliers dns server, just in case your local dns server does not include the online addresses your are trying for. Once you first setup your local dns cache server, there will not be addresses in your dns server, so your dns server will need to have the ability to discover this address somewhere.

You web suppliers dns deal with could be found utilizing many alternative strategies, so I'll explain only a few of those ways. If you're are using a router strive typing one of these addresses to access your default gateway. Open a web browser and kind in 192.168.1.1 or 192.168.1.254 within the deal with bar. In case you are utilizing a 2wire gateway the tackle will probably be 192.168.1.254, and if you are utilizing one other router reminiscent of a Linksys router, the handle might be 192.168.1.1.

If you are on a Windows based laptop, merely open up the command immediate by going to Start --> Accesories --> Command Prompt, or search for "cmd". After getting the command immediate open, sort in ipconfig /all. After getting typed the ipconfig /all command simply look though the listing for Domain name system servers. In the event you still don't know what the hell I am speaking about you may also use the handle 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

Ensure you add 127.0.0.1 to the file, since this may inform the resolv.conf file to have a look at you local host first for the dns translation. As you 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'm working a local dns server on my complete community, I've also added the handle 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 DNS/Gateway

After you have edited the /etc/resolv.conf file, you will want to edit yet another file. The final file that you might want 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've gotten edited the /etc/dhcp3/dhclient.conf file, the very last thing that you will need to do is restart dnsmasq to use the new changes.

/etc/init.d/dnsmasq restart

Article Source: http://depositarticles.com/

Linux Local DNS Cache Server Linux Network 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