NSEC3 proving non-existence of nic.mx/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of nic.mx/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
mx zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:1258::1, 2001:13c7:7000::1)
nic.mx zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:1258::1, 2001:13c7:7000::1)
nic.mx/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:1258::1, 2001:13c7:7000::1, UDP_-_NOEDNS_)
nic.mx/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:1258::1, 2001:13c7:7000::1, UDP_-_NOEDNS_)
nic.mx/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
NSEC3 proving non-existence of nic.mx/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of nic.mx/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
nic.mx/DS has warnings; select the "Denial of existence" DNSSEC option to see them.