Thanks for the suggestion. That does work, although it's a bit messy to
have to advertise a prefix you don't want the clients to use.
Cheers,
Christopher Martin
On Sun, Oct 28, 2018 at 7:41 AM Simon Kelley
wrote:
>
> Can you also add a dhcp-range for the ULA range, which deprecates it?
>
>
Thank you for the answer.
I suppose in this case I should enable inotify support in my Dnsmasq build.
Regards,
Mykola.
вс, 28 окт. 2018 г. в 14:14, Simon Kelley :
> The solution may be use of --hostsdir, which avoids the need for sending
> SIGHUP.
>
>
> Cheers,
>
> Simon.
>
>
> On 28/10/2018
Hi everybody,
I have a doubt and I can't found a solution...
Does anybody know, and can day me, if there is any way to configure DNSMasq to
asign IP depending if device type that requests the IP?
I want to define various IP Ranges to asign the IP depending, by example, if
the request came
Can you also add a dhcp-range for the ULA range, which deprecates it?
Cheers,
Simon.
On 27/10/2018 18:17, Christopher Martin wrote:
> Greetings,
>
> Is it possible to prevent Dnsmasq from advertising a specific prefix via
> router advertisements?
>
> Here's my situation. My ISP provides a
There's a CNAME at the root of the domain, which is not permissible, and
the root cause of the validation failure.
https://medium.freecodecamp.org/why-cant-a-domain-s-root-be-a-cname-8cbab38e5f5c
gives some reasons why this is not a good idea.
What actually happens is that dnsmasq makes a
The solution may be use of --hostsdir, which avoids the need for sending
SIGHUP.
Cheers,
Simon.
On 28/10/2018 10:55, Микола Василенко wrote:
> Hi all,
>
> Is there any method to avoid DNS cache clearing on SIGHUP? I want only
> to update host info by sending SIGHUP to dnsmasq daemon. As
Hi all,
Is there any method to avoid DNS cache clearing on SIGHUP? I want only to
update host info by sending SIGHUP to dnsmasq daemon. As there are no
servers info changed (e.i. resolv.conf, servers conf), I think, there is no
need to clear the cache as it is still up to date.
Thank in advance.
