dynect.net
Updated:
2022-05-27 02:29:27 UTC (940 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- dynect.net/A
- dynect.net/AAAA
- dynect.net/MX
- dynect.net/NS
- dynect.net/SOA
- dynect.net/TXT
Secure (2)
- net/SOA
- net/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- NSEC3 proving non-existence of dynect.net/DS
- net/DNSKEY (alg 8, id 35886)
- net/DNSKEY (alg 8, id 45728)
- net/DS (alg 8, id 35886)
Delegation status
Insecure (1)
- net to dynect.net
Secure (1)
- . to net
Notices
Errors (4)
- dynect.net zone: The following NS name(s) did not resolve to address(es): sydc01dns03.au.oracle.com, llg07dnsext01.llg.oracle.com, llg07dnsext02.llg.oracle.com, tvp02dnsext02.tvp.oracle.com, adc08dnsext01.us.oracle.com, adc08dnsext02.us.oracle.com, cgydc01dnsext01.us.oracle.com, rmdc02dnsext01.us.oracle.com, rmdc02dnsext02.us.oracle.com, trdc01dnsext01.us.oracle.com, iad-dns-master.oraclecorp.com
- dynect.net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (204.13.251.136, 208.78.71.136, 2001:500:94:1::136)
- dynect.net/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (204.13.251.136, 208.78.71.136, 2001:500:94:1::136, UDP_-_NOEDNS_)
- dynect.net/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (204.13.251.136, 208.78.71.136, 2001:500:94:1::136, UDP_-_NOEDNS_)
Warnings (8)
- net to dynect.net: Authoritative AAAA records exist for ns4.dynamicnetworkservices.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- net to dynect.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): trdc01dnsext01.us.oracle.com, iad-dns-master.oraclecorp.com, llg07dnsext01.llg.oracle.com, adc08dnsext01.us.oracle.com, sydc01dns03.au.oracle.com, rmdc02dnsext01.us.oracle.com, llg07dnsext02.llg.oracle.com, cgydc01dnsext01.us.oracle.com, tvp02dnsext02.tvp.oracle.com, adc08dnsext02.us.oracle.com, rmdc02dnsext02.us.oracle.com See RFC 1034, Sec. 4.2.2.
- net to dynect.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns1.dynamicnetworkservices.net, ns2.dynamicnetworkservices.net, ns3.dynamicnetworkservices.net, ns4.dynamicnetworkservices.net, ns5.dynamicnetworkservices.net, ns6.dynamicnetworkservices.net See RFC 1034, Sec. 4.2.2.
- net to dynect.net: The glue address(es) for ns3.dynamicnetworkservices.net (2001:500:94:1::136) differed from its authoritative address(es) (2600:2000:2230::136). See RFC 1034, Sec. 4.2.2.
- net to dynect.net: The glue address(es) for ns3.dynamicnetworkservices.net (208.78.71.136) differed from its authoritative address(es) (108.59.163.136). See RFC 1034, Sec. 4.2.2.
- net to dynect.net: The glue address(es) for ns4.dynamicnetworkservices.net (204.13.251.136) differed from its authoritative address(es) (108.59.164.136). See RFC 1034, Sec. 4.2.2.
- net to dynect.net: The glue address(es) for ns6.dynamicnetworkservices.net (2001:500:94:1::136) differed from its authoritative address(es) (2600:2000:2230::136). See RFC 1034, Sec. 4.2.2.
- net to dynect.net: The glue address(es) for ns6.dynamicnetworkservices.net (208.78.71.136) differed from its authoritative address(es) (108.59.163.136). See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
