[Dnsmasq-discuss] Adding wildcard entries for DHCP lease host names

Hello, To make it easy to share links to locally-installed web projects on developer machines (accessible via "projectname.devmachine"), I want to have dnsmasq automatically create wildcard entries for the host names of DHCP leases. For example, when a dev machine requests an IP via DHCP

Re: [Dnsmasq-discuss] Same hostname in different domains with dhcp static assignments?

Turns out I needed dhcp-fqdn set... just setting the domain name isn't enough Sorry to have bothered ya On Tue, Jan 26, 2016 at 7:05 PM, Steve Hindle wrote: > Hi! > I seem to have an odd issue with static dhcp reservations on multiple > networks with the same hostname but

Re: [Dnsmasq-discuss] No caching unless recursion enabled?

Thanks for that, so essentially I need to download the source code, modify and recompile? There is no simple way for me to otherwise do this with my current installation, as that isn't really an option in this environment. A configuration option to enable this would be great, but understand

Re: [Dnsmasq-discuss] prevent dnsmasq from releasing IPs

Am 25.01.2016 um 23:20 schrieb Simon Kelley: > Not directly. If you just want a record of leases after they've been > released, then you can save information by using the dhcp-script > function. If you want to stop re-use of the addresses, then the best > you can easily do is to allocate static

Re: [Dnsmasq-discuss] prevent dnsmasq from releasing IPs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 26/01/16 07:25, Stefan Priebe - Profihost AG wrote: > > > Am 25.01.2016 um 23:20 schrieb Simon Kelley: >> Not directly. If you just want a record of leases after they've >> been released, then you can save information by using the >>

Re: [Dnsmasq-discuss] prevent dnsmasq from releasing IPs

Am 26.01.2016 um 14:32 schrieb Simon Kelley: > > > On 26/01/16 07:25, Stefan Priebe - Profihost AG wrote: > > >> Am 25.01.2016 um 23:20 schrieb Simon Kelley: >>> Not directly. If you just want a record of leases after they've >>> been released, then you can save information by using the >>>

Re: [Dnsmasq-discuss] prevent dnsmasq from releasing IPs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 26/01/16 13:42, Stefan Priebe - Profihost AG wrote: > > > what about writing and sending kill 1 / HUP? > No. The only only way to make that work would be to 1) Stop dnsmasq with SIGTERM 2) modify the leases file 3) restart dnsmasq in

Re: [Dnsmasq-discuss] prevent dnsmasq from releasing IPs

> Am 26.01.2016 um 14:46 schrieb Simon Kelley : > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > >> On 26/01/16 13:42, Stefan Priebe - Profihost AG wrote: > >> >> what about writing and sending kill 1 / HUP? > > > No. The only only way to make that work

Re: [Dnsmasq-discuss] prevent dnsmasq from releasing IPs

On 26/01/16 15:09, Stefan Priebe - Profihost AG wrote: >> Am 26.01.2016 um 14:46 schrieb Simon Kelley : >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> >> >>> On 26/01/16 13:42, Stefan Priebe - Profihost AG wrote: >>> what about writing and sending kill 1 /

Re: [Dnsmasq-discuss] prevent dnsmasq from releasing IPs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 26/01/16 14:56, Stefan Priebe - Profihost AG wrote: > >> Am 26.01.2016 um 14:46 schrieb Simon Kelley >> : >> > > On 26/01/16 13:42, Stefan Priebe - Profihost AG wrote: > what about writing and

Re: [Dnsmasq-discuss] prevent dnsmasq from releasing IPs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 26/01/16 16:03, Neil Jerram wrote: > On 26/01/16 15:09, Stefan Priebe - Profihost AG wrote: >>> Am 26.01.2016 um 14:46 schrieb Simon Kelley >>> : >>> >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >>> >>> >>>

[Dnsmasq-discuss] Same hostname in different domains with dhcp static assignments?

Hi! I seem to have an odd issue with static dhcp reservations on multiple networks with the same hostname but different domains (eg ' foo.ipmi.example.com' and 'foo.hvm.example.com'). I am setting static assignments for both interfaces via: dhcp-host=,,, Basically seems to break DNS lookup for me

[Dnsmasq-discuss] Does dhcp-range accept/require an interface for ipv4

Hi! When dealing with multiple interfaces/subnet, should dhcp-range be given the interface? I only see it mentioned for ipv6 stuff in the manpage, but I'm finding stuff online that says to use: dhcp-range=eth1,172.16.49.101,172.16.49.254,14400 or: