On Fri, Jul 24, 2009 at 5:09 AM, Rance Hall<ran...@gmail.com> wrote: > On Fri, Jul 24, 2009 at 3:54 AM, Stefano Bridi<stefano.br...@gmail.com> wrote: >> Hi all, first of all thanks for the wonderful tool! >> I have a problem with the dns part of dnsmasq: sometimes does not >> resolve hostnames. > There are two things that I want to point you to: > > 1) the local=/domain.tld/ option > > if you specify this option correctly then members of that domain are > never forwarded to isp. This option will fix your problem of > forwarding names to the public internet that dont exist. and should > speed things up right off. > > 2) while the above is good advice, its not complete, it doesnt fix the > problem of dnsmasq not knowing about the boxes on the localnet in the > first place. > > On its face, I'd say that this is a configuration error. In all my > years of using dnsmasq Ive never seen this problem on a otherwise > correctly configured dnsmasq that wasnt my fault. > > the way you have dnsmasq configured local queries only come from one > of two places, the alternate host file you specified, and the dhcp > leases file. > > Make absolutely sure that the host you are occasionally having trouble > with is actually present in either one of these files. I suspect it > is not present at the point you are having the trouble. > > HTH > > Rance >
Oh and I forgot one other thing, I use TWO resolv.conf files Rather than listing them in the config file I have a /etc/resolv.conf file that points the server box back to itself as you do, But I also have a /etc/resolv.conf.forwards file that has the nameservers from the isp in the proper resolv.conf format. then I dont have the entries in the config file. Its not that one way is better than the other, but I find that its easier to troubleshoot problems like this when you know exactly which configuration file is causing you problems and the fact that each file is not that large so it makes mistakes easier to spot. Just a thought. HTH
