In reply to a post by GraceCourt:

However, hopefully Zen will resolve the zone file problem tomorrow morning and it should begin propagating around the Internet thereafter.

Update: Apart from some messages to Yahoo/AOL still being stuck in the mail queue, which is a propagation issue and not directly Zen's fault, all seems to be well now.

Interestingly, Zen only added an ARPA PTR record for the subnet 51.155.204.0/24 to the relevant zone file, so it looks like it's company policy only to add these PTR records long after... ermmm, I mean, shortly before(!) they start allocating the affected IP addresses to customers. To my mind, and bearing in mind that propagation delays in propagating zone files can in practice be measured in days, it would make sense to ensure that such amendments are made at least a week in advance.

But obviously not at Zen: they've stayed tight-lipped about why they goofed so badly here.

In reply to a post by tdw42:

I've explained it again, waiting to see what happens next....

See my latest post: if your third quadret isn't 204, you could try speeding things up by updating your trouble ticket, quoting my ticket number 02468233, and saying it's the same problem. Good luck!

Edited by deleted (Tue 10-May-22 16:45:05)

Thanks, it isn't.

As first line support have said it is beyond their knowledge scope and is being referred to the networks team I've provided that information. Hopefully they might fix the problem for all of their broken /24 blocks.

In reply to a post by tdw42:

Despite providing the nslookup results showing the SOA records are missing for the /24 block in question the first response I've had is to set my rDNS through the portal, which is not the issue. I've explained it again, waiting to see what happens next....

This is honestly the most frustrating update to receive in a support case. I'm running out of different ways to say "please read the issue again and come up with a response that is on-topic".

In reply to a post by GraceCourt:

Addendum - the affected IP address range is slightly larger than stated above, there are ARPA NS records for most of the 51.155.0.0/24 sub-nets...

Update: Just in case anyone in future finds this thread when they'e having problems with Zen rDNS, the delegated zone file for 155.51.in-addr.arpa now contains PTR records for all of the 51.155.0.0/24 sub-nets. So rDNS now works properly for all IP addresses in 51.155.0.0/16

But it still shouldn't ever have happened.