Same here, 212.0.0.0/8 is impacted and causing us problems - I'm trying the workaround of editing the database entries that someone else suggested and that seems to work so far. On 14/06/12 09:49, igor.grinevich@vegatele.com wrote:
Hi!
We have the same issue with some reverse zones хх.хх.212.in-addr.arpa. Does anyone get a feedback about the probleb from Ripe?
Regards, Igor Grinevich Vega
-----Original Message----- From: members-discuss-bounces@ripe.net [mailto:members-discuss-bounces@ripe.net] On Behalf Of Raymond Dijkxhoorn Sent: Thursday, June 14, 2012 9:31 AM To: members-discuss-bounces@ripe.net Cc: Jørgen Hovland; members-discuss@ripe.net Subject: Re: [members-discuss] Reverse DNS issue - zone still not working fromripe DNS server
Hi!
after the issue the ripe services had today evening, we still have one network whre delegation for reverse is still not working.
Of course this is a nightmare as all mail traffic is affected.
Anyone know a way to contact ripe support outside of office hours ? Jun 14 07:23:47 infra20 unbound: [6960:1] info: validation failure <102.162.179.212.in-addr.arpa. PTR IN>: key for validation 179.212.in-addr.arpa. is marked as invalid because of a previous validation failure <102.162.179.212.in-addr.arpa. PTR IN>: no NSEC3 records from 192.134.0.49 for DS 179.212.in-addr.arpa. while building chain of trust Jun 14 07:24:47 infra20 unbound: [6960:1] info: validation failure <102.162.179.212.in-addr.arpa. PTR IN>: key for validation 179.212.in-addr.arpa. is marked as invalid because of a previous validation failure <102.162.179.212.in-addr.arpa. PTR IN>: no NSEC3 records from 192.134.0.49 for DS 179.212.in-addr.arpa. while building chain of trust Jun 14 07:26:06 infra20 unbound: [6960:1] info: validation failure <102.162.179.212.in-addr.arpa. PTR IN>: key for validation 179.212.in-addr.arpa. is marked as invalid because of a previous validation failure <102.162.179.212.in-addr.arpa. PTR IN>: no NSEC3 records from 192.134.0.49 for DS 179.212.in-addr.arpa. while building chain of trust Jun 14 07:27:09 infra20 unbound: [6960:1] info: validation failure <102.162.179.212.in-addr.arpa. PTR IN>: key for validation 179.212.in-addr.arpa. is marked as invalid because of a previous validation failure <102.162.179.212.in-addr.arpa. PTR IN>: no NSEC3 records from 192.134.0.49 for DS 179.212.in-addr.arpa. while building chain of trust Jun 14 07:38:10 infra20 unbound: [6960:1] info: validation failure <102.162.179.212.in-addr.arpa. PTR IN>: no NSEC3 records from 202.12.28.140 for DS 179.212.in-addr.arpa. while building chain of trust
This still was happening on several zones up to one hour ago. Since this is impacting the real world pretty badly i would expect a bit more fuzz. Mailflows are impacted with this, providers rejecting mails due to missing and/or invalid rdns...
Bye, Raymond.
---- If you don't want to receive emails from the RIPE NCC members-discuss mailing list, please log in to your LIR Portal account and go to the general page: https://lirportal.ripe.net/general/view
Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses. ---- If you don't want to receive emails from the RIPE NCC members-discuss mailing list, please log in to your LIR Portal account and go to the general page: https://lirportal.ripe.net/general/view
Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses.