AW: Problem resolving a host wenn TTL of NS-Servers runs out

[Melbinger Christian]

Hi

I strongly disagree, as I already start the daemon with the -4 option. It should never user IPv6.

-4 This option tells named to use only IPv4, even if the host machine is capable of IPv6. -4 and -6 are mutually exclusive.
https://bind9.readthedocs.io/en/v9.18.14/manpages.html#named-internet-domain-name-server


And also I just tried it, I added the line under options and reloaded the daemon with
docker exec -ti named-prod /usr/sbin/rndc reload

It's still not working. there's only the AAAA IP in the cache, and it can never reach it...

Regards,
Christian

-----Ursprüngliche Nachricht-----
Von: Colin Vidal <colin at isc.org>
Gesendet: Montag, 26. Jänner 2026 16:48
An: Melbinger Christian <Christian.Melbinger at wienit.at>
Cc: bind-users <bind-users at lists.isc.org>
Betreff: Re: Problem resolving a host wenn TTL of NS-Servers runs out

[You don't often get email from colin at isc.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

Hi,

> Short version: When a NS has A and AAAA Records with different TTLs, a
> bind with only IPv4 fails to resolve an address once the A-Record
> expires and only the AAAA is left.

I think `query-source-v6 none;` in `options` should solve your problem.

https://bind9.readthedocs.io/en/v9.20.18/reference.html#namedconf-statement-query-source-v6

--
Colin Vidal -- colin at isc.org
Internet Systems Consortium
____________________________________________________________________________

WienIT GmbH, Thomas-Klestil-Platz 13, 1030 Wien,
FN 255649 f, Handelsgericht Wien,  DVR: 2109667, UID-Nr. ATU61296118