Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I have a rather large home network, which is used by the family. A performance issue appears to be that with everyone's activity, there are lots of DNS hits. The local ISP is slow, but there are some other alternatives like OpenDNS, which may perform faster.
What I would really like to try is to cache dns calls locally. For lots of reasons, all the machines here have static IPs, so using the DNS caching capability of dnsmasq is apparently not an option.
Can anyone point out what options I might have? I'd like to cache a small number of DNS calls, (~1000 to 5000), and have DNS run through my gateway slackware 12.1 box. That box would make outside queries for addresses not in the cache, or for which the cache was getting stale on.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
dnsmasq provides for dns cacheing of dhcp clients. Since my IPs are static, DHCP is not used for any of them, and therefore the dnsmasq dns cacheing capability cannot be used.
This is incorrect - you may give out static IP's through static DHCP and Dnsmasq is set up to do this if you wish. Simply build a table in dnsmasq mapping ip's to mac addresses and then those IP's will always be given out to the same clients.
I had my network setup this way as it eased setting up gateway and nameserver addresses across the network.
This is defined in the DHCP RFC 2131 here and is known as manual allocation. It forms part of the standard.
You may use dnsmasq in your case in fact it's ideally suited and will cut configuration and administration as well as speeding up DNS access.
It doesn't ! Dnsmasq handles DHCP, DNS forwarding and caching. It's DHCP may be static or even disabled and it's DNS caching may handle all requests should you so desire.
You are right! I fired up dnsmasq, and low and behold, it started serving dns. I'm not clear on how much it cached, because the times on repeated dns requests does not drop much. I can investigate further.