Stéphane Bortzmeyer

\pied semble obligatoire

7

La documentation ne le dit apparemment pas mais la commande \pied semble obligatoire. ``` ! Undefined control sequence. \f@nch@orf ->\@pied \strut l.17 \end{document} ? ```

BIND auto-signing or validns?

6

I get an error: ``` % validns -p all -z example example.signed-text example.signed-text:15: example. RRSIG(TYPE65534): bad signature example.signed-text:3: example. RRSIG(SOA): bad signature ``` The zone is maintained by BIND "auto-dnssec...

Add support for ILNP records

4

The codes for the four ILNP records (NID, L64, L32 and LP) have been added to the IANA registry http://www.iana.org/assignments/dns-parameters. The future RFC is in the RFC Editor Queue http://www.rfc-editor.org/internet-drafts/draft-irtf-rrg-ilnp-dns-06.txt...

When we use the -ns option, it is often because there is a problem resolving the names. Therefore, IWBNI we could specify name servers by IP addresses: ``` % check-soa...

If a name server has a name but no IP address (here, the example uses the existing TLD "foo"), it is silently ignored: ``` % check-soa -ns "foo d.nic.fr" fr...

Depending on the local resolver has some consequences

1

check-soa uses the local resolver to retrieve the list of NS. For instance, if the local resolver validates with DNSSEC _and_ the domain is broken (.MIL, today), the message is...

When there is no connectivity at all, and the resolver replies SERVFAIL, the error message is "No NS records for "demaziere.fr.". It is probably a domain but not a zone"...

The default behavior, testing each IP address of each name server name is OK (a machine may work with IPv4 but not IPv6, for instance). But it would be nice...

https://dns.bortzmeyer.org/xn--kprw13d/DNAME Unknown record type (39)

When using a validating resolver, we should display the result of validation (the AD bit).