Hi Chris, Petr
I agree with Chris: I wish we could disable IPv6 support.
There are scenarios - like usage in intranet LANs, IPv4 only - this feature is
useless.
For best practice, unwanted features should be disabled:
1) avoid any possibility of hitting bugs in code paths that implemet this
Hi
Please I need a little help.
This files are the configuration:
/etc/hosts
127.0.0.1 localhost localhost.example.local postgresqldb
postgresqldb.example.local
dnsmasq.conf
# don't read /etc/resolv.conf
no-resolv
domain=example.local,10.0.0.0/8
domain-needed
Hi
I compile dnsmasq 2.80, without dhcp support.
dnsmasq -v
Dnsmasq version 2.80 Copyright (c) 2000-2018 Simon Kelley
Compile time options: no-IPv6 GNU-getopt no-DBus no-i18n no-IDN no-DHCP
no-scripts no-TFTP no-conntrack ipset no-auth no-DNSSEC loop-detect no-inotify
dumpfile
dnsmasq
help about dhcp features.
However, thank you for your suggestion.
It suggests to me to check with dnsmasq 2.80.
Best regards, Massimo
Da: SALA MASSIMO
Inviato: giovedì 13 giugno 2019 12:04:57
A: Kevin Darbyshire-Bryant
Cc: dnsmasq-discuss@lists.thekelleys.org.uk
Hi Kevin
Massimo wrote:
A quick glance at the source code: it seem to me the help arguments aren't
conditioned by the compilation macros.
Kevin wrote:
... we look (& parse) the output of ‘dnsmasq -v’ at run-time to determine what
build-time options have been selected.
Mmh we are saying
ompilation and dependencies
On Wed, Jun 12, 2019 at 03:19:04PM +0000, SALA MASSIMO wrote:
> Hi
>
>
> I have some servers with linux 2.6.18.
>
> I know... but I cannot upgrade because of legacy applications,
> it's ok for us, they are only for intranet usage.
>
>
> Pls a few questions:
Hi
I have some servers with linux 2.6.18.
I know... but I cannot upgrade because of legacy applications, it's ok for us,
they are only for intranet usage.
Pls a few questions:
1) configure and compile vs dnsmasq --help
I want only the DNS daemon, a minimal version (not authoritative).
I
