[DNSSEC-Ops] Help

[Amreesh Phokeer]

Hi Ahmed,

> On 17 Oct 2018, at 00:17, Ahmed ZERKOUK <Ahmed.ZERKOUK at icosnet.com> wrote:
> 
> The authoritative  name server for 11.140.197.in-addr.arpa is dns1.icosnethosting.com.

Have you signed the zone? I was not able to retrieve the DNSKEY from the zone.
Once you have the DNSKEY, you can generate the DS and send it to the parent.

> 
> Also we have the same problem with for ex. 9.140.197.in-addr.arpa that have ns1.aloline.com as authoritative name server .

See errors from DNSViz

http://dnsviz.net/d/9.140.197.in-addr.arpa/dnssec/

Errors (5)
	• 9.140.197.in-addr.arpa zone: The server(s) did not respond authoritatively for the namespace. (196.41.225.10, 196.41.225.11)
	• 9.140.197.in-addr.arpa/MX (NODATA): The response was an upward referral. (196.41.225.10, 196.41.225.11, UDP_0_EDNS0_32768_4096, UDP_0_EDNS0_32768_512)
	• 9.140.197.in-addr.arpa/NS (NODATA): The response was an upward referral. (196.41.225.10, 196.41.225.11, UDP_0_EDNS0_32768_4096)
	• 9.140.197.in-addr.arpa/SOA (NODATA): The response was an upward referral. (196.41.225.10, 196.41.225.11, TCP_0_EDNS0_32768_4096, UDP_0_EDNS0_32768_4096)
	• 9.140.197.in-addr.arpa/TXT (NODATA): The response was an upward referral. (196.41.225.10, 196.41.225.11, UDP_0_EDNS0_32768_4096)
Warnings (2)
	• in-addr.arpa to 197.in-addr.arpa: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the in-addr.arpa zone): ns2.lacnic.net
	• in-addr.arpa to 197.in-addr.arpa: The following NS name(s) were found in the delegation NS RRset (i.e., in the in-addr.arpa zone), but not in the authoritative NS RRset: ns3.lacnic.net

Regards,
Amreesh