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 possib
Hi,
171.in-addr.arpa was also affected only that works since the ARIN is fixed.
171.in-addr.arpa is a APNIC zone I think.
Martin
Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
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, Heik
having 96.153.in-addr.arpa and 97.153.in-addr.arpa
Heike
Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
APNIC problem with delegations ?
dig @8.8.8.8 ptr 11.10.109.153.in-addr.arpa
153.in-addr.arpa. 1657 IN SOA ns1.apnic.net.
read-txt-record-of-zone-first-dns-admin.apnic.net. 48427 7200 1800
604800 172800
VSnet
our 153.in.addr.arpa does not work correctly, could you please check.
Tanks, Hei
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
Dear colleagues,
Between 17:00 UTC yesterday and 10:00 UTC today, we had an issue that
affected some reverse DNS delegations. The delegations in the
RIPE Database where the parent zone is operated by ARIN were affected.
RIPE NCC publishes zonelet files containing these delegations, and these
are
