-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dear Reihaneh, Please find attached our reply to your question. Regards,
-------- Original Message -------- Subject: FW: FAILED: reverse Date: Sun, 6 Oct 2013 14:14:23 +0330 From: javidi <ripe@dci.ir> To: <db-help@ripe.net>
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.
11:04:21-iortiz~$ dig ns 140.38.78.in-addr.arpa @ns1.parsdata.com +short parsdata-helm. 11:05:58-iortiz~$ dig ns 140.38.78.in-addr.arpa @ns2.parsdata.com +short 11:06:01-iortiz~$ ns2.parsdata.com returns NXDOMAIN. ns1.parsdata.com returns invalid answers (see below).
***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.
10:58:26-iortiz~$ dig @ns24.parsweb.com ns1.parsdata.com +short 217.66.216.70 10:58:29-iortiz~$ dig @ns24.parsweb.com ns2.parsdata.com +short 217.66.216.80 10:58:32-iortiz~$ dig @ns25.parsweb.com ns1.parsdata.com ; <<>> DiG 9.8.3-P1 <<>> @ns25.parsweb.com ns1.parsdata.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached 10:58:58-iortiz~$ dig @ns25.parsweb.com ns2.parsdata.com ; <<>> DiG 9.8.3-P1 <<>> @ns25.parsweb.com ns2.parsdata.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached ns25.parsweb.com seems to be unavailable.
***Error: No address found for parsdata-helm.
No IPv4 or IPv6 address was found for the host name.
Explained next.
***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.
The MNAME of the SOA record in the zone file defined on their auth servers (ns[12].parsdata.com) must be the valid hostname of the master server (unless a hidden master setup is in use, which is not the case most surely)
***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.
The RNAME of the SOA record in the zone file defined on their auth servers must have the correct syntax, outlined above.
***Warning: Error while checking SOA MNAME for 140.38.78.in-addr.arpa (parsdata-helm).
The SOA MNAME is not a valid host name.
Ditto
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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)
In summary, all the issues reported above must be fixed before he can re-attempt to delegate or we help them further - should he still get the errors. -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org iQEcBAEBCgAGBQJSUolOAAoJELPfvrguw2h1hP0H/R6RGB+gBFXqI7yrNCerE/bm Hln00OVOwtRj6JNe7F/aM5xfxXq7vFbVBAU7PEAjQyUQxlF4RPYowiv44d/5fsed FPdVZ0/0MvCMro8lFN9ag2/bRGXxi+vLUCfFf+VNxOGOfnCtIvCw8XLkWoqnA3lY /b/xgR2wRW6oGcewStndolinTRkSS8x1pHKPX6xmL+Ee9ok/BxNebFteqJ/XNoyJ +b+yryLp1shd7o5qJ/xRrYn0MX47yj6TAQd7XJY/ArhCJytvjn7tKFs/dL9+9xbU jmR6+gS8XLzagVglVNqoGUYv8NN7baY4bLuKANJ+5j0tt1OLtjYvmEhdwmsLLVc= =LU6+ -----END PGP SIGNATURE-----