On Sun, Dec 08, 2024 at 09:20:13AM +0100, Florian Obser wrote:
> RESINFO is just a weird spelling for txt:
> 
> | 4. Format of the Resolver Information
> |
> | The resolver information record uses the same format as DNS TXT records.
> 
> It can be tested thusly:
> 
> $ dig @resolver64.dns4all.eu resolver64.dns4all.eu RESINFO
> 
> ; <<>> dig 9.10.8-P1 <<>> @resolver64.dns4all.eu resolver64.dns4all.eu RESINFO
> ; (2 servers found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29370
> ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
> 
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 1232
> ;; QUESTION SECTION:
> ;resolver64.dns4all.eu.		IN	RESINFO
> 
> ;; ANSWER SECTION:
> resolver64.dns4all.eu.	2551	IN	RESINFO	"qnamemin temp-dnssecval temp-dns64 infourl=https://dns4all.eu"
> 
> ;; Query time: 46 msec
> ;; SERVER: 2001:678:8::64#53(2001:678:8::64)
> ;; WHEN: Sun Dec 08 09:12:38 CET 2024
> ;; MSG SIZE  rcvd: 124
> 
> 
> btw. I don't think dns4all.eu implements RESINFO correctly.
> 
> | The DNS client MUST set the Recursion Desired (RD) bit of the query to
> | 0. The DNS client MUST discard the response if the AA flag in the
> | response is set to 0, indicating that the DNS resolver is not
> | authoritative for the response.
> 
> The answer does not have AA set and if I query with +norec I get
> REFUSED. But never mind that, that's a problem on the server side.
> 
> OK?

OK caspar@