[Dnsmasq-discuss] dnsmasq's behaviour with configured static hosts is unintuitive
Geert Stappers
stappers at stappers.nl
Sat Mar 6 19:22:59 UTC 2021
On Thu, Mar 04, 2021 at 06:50:39AM +0000, Aaron Jones wrote:
> Hello.
>
> I'm trying to force queries for specific names to not be forwarded along
> to recursors, and be answered locally. The normal way to do this is to
> put such address/name pairs in hosts(5), or you can add a --host-record=
> option to the configuration file.
>
> That works okay.
Acknowledge
> However, I'm trying to force a specific address family. Specifically,
> these records are for host names on a VPN, and the VPN is IPv6 only. So,
> for example, given the following configuration option:
>
> --host-record=foo.example.org,fd00::1
>
> Or given the following hosts(5) entry:
>
> fd00::1 foo.example.org
>
> ... will result in an AAAA query for the name returning fd00::1, but an
> A query is forwarded along to the configured recursors, instead of
> dnsmasq replying with NODATA.
>
> This seems wrong.
I don't think so.
Infact it is what dnsmasq does
- reply with what it knows
- otherwise forward the request
> I tried to explicitly indicate that there is no IPv4 address, but this
> option has no effect:
>
> --host-record=foo.example.org,,fd00::1
>
> ... and this option returns the address exactly as given:
>
> --host-record=foo.example.org,0.0.0.0,fd00::1
>
> Any pointers?
Share the challenge you are facing with us.
Groeten
Geert Stappers
--
Silence is hard to parse
More information about the Dnsmasq-discuss
mailing list