17 Mar
2017
17 Mar
'17
3:15 p.m.
109.153.in-addr.arpa ok since 5 minutes Thanks. VSnet
Hello Heike,
Thank you for reporting this. We're looking at it now. My analysis shows that two out of 4 APNIC-operated zones are affected as well:
153.in-addr.arpa 163.in-addr.arpa
We are attempting to resolve this as soon as possible.
Regards, Anand Buddhdev RIPE NCC
On 17/03/2017 13:15, Heike Schwingel-Horner wrote:
our 153.in.addr.arpa does not work correctly, could you please check. Tanks, Heike
Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum