Dear Sir/Madam I sent the form below to define reverse DNS for a customer. But these errors appear. Please inform me to tell him how to fix these errors. My next question is about reverse delegation for assignments </24. I've read page 111 Lir HAND BOOK.but I can't define reverse dns for less than /24. Best Regards Reihaneh Javidi. -----Original Message----- From: RIPE Database Administration local [mailto:unread@ripe.net] Sent: Sunday, October 06, 2013 1:45 PM To: ripe@dci.ir Subject: FAILED: reverse

From: javidi <ripe@dci.ir> Subject: reverse Date: Sun, 06 Oct 2013 12:14:03 +0200 Reply-To: javidi <ripe@dci.ir> Message-ID: <00d401cec27c$9c8e7c80$d5ab7580$@ir>

SUMMARY OF UPDATE: Number of objects found: 1 Number of objects processed successfully: 0 Create: 0 Modify: 0 Delete: 0 No Operation: 0 Number of objects processed with errors: 1 Create: 1 Modify: 0 Delete: 0 DETAILED EXPLANATION: ***Warning: Invalid keyword(s) found: reverse ***Warning: All keywords were ignored ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following object(s) were found to have ERRORS: --- Create FAILED: [domain] 140.38.78.in-addr.arpa domain: 140.38.78.in-addr.arpa descr: Reverse Delegation for ikk.ir IP range. admin-c: MT7308-RIPE tech-c: MT7308-RIPE zone-c: MT7308-RIPE nserver: ns1.parsdata.com nserver: ns2.parsdata.com mnt-by: AS12880-MNT notify: javadshoaei@yahoo.com changed: ripe@dci.ir 20131006 source: RIPE ***Error: Superfluous name server listed at parent: ns1.parsdata.com A name server listed at the parent, but not at the child, was found. This is most likely an administrative error. You should update the parent to match the name servers at the child as soon as possible. ***Error: Superfluous name server listed at parent: ns2.parsdata.com A name server listed at the parent, but not at the child, was found. This is most likely an administrative error. You should update the parent to match the name servers at the child as soon as possible. ***Error: Total parent/child glue mismatch. The parent lists name servers that the child doesn't know about; see details in advanced. This configuration could actually work but breaks very easily if one of these zones changes slightly. ***Error: No address found for parsdata-helm. No IPv4 or IPv6 address was found for the host name. ***Error: Host name or address error for parsdata-helm. The specified host name is not a valid host name or the host name points to an invalid IP address, e.g. a private or reserved IP address. ***Error: Invalid SOA RNAME syntax for 140.38.78.in-addr.arpa: hostmaster The email address specified in SOA RNAME is specified incorrectly. A common error is to use @ in the address field - an address like hostmaster@example.com must be specified as hostmaster.example.com. ***Warning: Error while checking SOA MNAME for 140.38.78.in-addr.arpa (parsdata-helm). The SOA MNAME is not a valid host name. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The RIPE Database is subject to Terms and Conditions: http://www.ripe.net/db/support/db-terms-conditions.pdf For assistance or clarification please contact: RIPE Database Administration <ripe-dbm@ripe.net> Generated by RIPE WHOIS Update version 1.69 on WHOIS4 Handled email update (RIPE, 2013-10-06 12:14:40)