[Dnsmasq-discuss] Re: resolver options

[AJ Weber]

Thank you for your quick reply...

RE: "options in the custom resolver file", should we have the ability to propagate some of these options?  For example, timeout, attempts and rotate?  I think they could be useful in certain situations (like my own...I don't want to have to update all my clients resolv interaction -- or can this be set with a dhcp option of sorts?).

RE: The existing leases...I knew the leases were cached in a file, but I didn't know that when dnsmasq starts it actually reads the file and leverages that information.  Is that documented somewhere?

I've said it before, and I'll say it again:  This is a fantastic piece of software!

Thanks again,
AJ

  ----- Original Message ----- 
  From: Simon Kelley 
  To: AJ Weber 
  Cc: dnsmasq-discuss at lists.thekelleys.org.uk 
  Sent: Tuesday, February 06, 2007 12:42 PM
  Subject: Re: resolver options


  AJ Weber wrote:
  > 
  > If I use a "different" resolv.conf file (i.e. I use a 
  > resolv-file=/etc/resolv.dnsmasq), will an "option" have the same effect 
  > it normally would?
  >  
  > For example, I'm considering changing timeout to 2 (instead of the 
  > default of 5), because I've had some issues with my ISP's DNS servers 
  > recently and don't want to wait too long for the timeout.  With the 
  > broadband connection, any of the nameservers in my list consistenly 
  > returns in < 1 sec (when they're up, of course).
  >  
  > Will this have the desired effect?  Any comments or concerns with that 
  > change in general?  Am I misunderstanding the purpose of the "options 
  > timeout:" ?

  The only lines which are read by dnsmasq are "nameserver" ones - 
  everything else is ignored, except "search" if the option --domain=# id 
  used, when the first entry of the search string is used as dnsmasq's 
  domain setting.

  To get the effect of faster time-outs, it's necessary to alter the 
  timeout in the clients, not in dnsmasq.
  >  
  > ALSO...(DIFFERENT TOPIC) : Is there no way to tell dnsmasq to dump it's 
  > current lease-info to a file that could be read on restart so it knows 
  > about all outstanding DHCP leases?  It's rare that I have to restart 
  > dnsmasq or the linux box it's on, but when I do, it forces me to restart 
  > a lot of client machines in case I'd get a dhcp/IP address mix-up (where 
  > dnsmasq doesn't know an IP Address is already leased to a running 
  > client, and a new client requests a lease so it hands-out the same 
  > address).

  Dnsmasq does this by default, in /var/lib/misc/dnsmasq.leases. You can 
  change the location of the lease file using --dhcp-leasefile.

  Cheers,

  Simon.

  >  
  > Thanks in advance,
  > AJ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20070206/0c86a2c4/attachment.htm