Yes, use "static" in the dhcp-range definition.
The man page is quite helpful.
On Wed, Apr 13, 2011 at 1:34 PM, Scott wrote:
> Hello,
>
>
>
> Is there a way to have dnsmasq only serve IP’s if a reservation exists for
> that IP? And if no IP reservation exists, for it to hold onto that IP
> (sim
Hello,
Is there a way to have dnsmasq only serve IP's if a reservation exists for
that IP? And if no IP reservation exists, for it to hold onto that IP
(similar to Windows DHCP where you exclude the entire range, and then it
will only serve IP's if a reservation exists)?
Warm regards,
Sco
On Wed, Apr 13, 2011 at 10:42 PM, /dev/rob0 wrote:
> Right. I like using a dnsmasq.d directory for things like that, where
> records for a specific purpose are in their own modular file:
>conf-dir=/etc/dnsmasq.d
>
Thanks. :)
On Wed, Apr 13, 2011 at 10:25:55PM +0530, Mohit Chawla wrote:
> On Wed, Apr 13, 2011 at 9:25 PM, /dev/rob0 wrote:
>
> > The hosts(5) file format is far simpler than a DNS zone file or a
> > dnsmasq(8) config file. "IP.add.re.ss name [alias ...]". dnsmasq
> > assumes that the presence of a hosts
Hi,
On Wed, Apr 13, 2011 at 9:25 PM, /dev/rob0 wrote:
> The hosts(5) file format is far simpler than a DNS zone file or a
> dnsmasq(8) config file. "IP.add.re.ss name [alias ...]". dnsmasq
> assumes that the presence of a hosts listing for IP.add.re.ss means
> that you want a PTR for "ss.re.add
On Wed, Apr 13, 2011 at 11:30:31AM +0530, Mohit Chawla wrote:
> On Wed, Apr 13, 2011 at 1:19 AM, Mohit Chawla
> wrote:
>
> > I need to validate the correct behavior of dnsmasq when serving
> > ptr records.
>
> I must have missed something before, things are working similarly
> on CentOS and D
On Wed, Apr 13, 2011 at 1:19 AM, Mohit Chawla wrote:
> I need to validate the correct behavior of dnsmasq when serving ptr
> records.
>
I must have missed something before, things are working similarly on CentOS
and Debian. Although I haven't added any ptr-record lines in the hosts file,
answers
