DNS updates and Apple Private Relay - major issue

After dropping an A-record TTL to 60 secs (it was previously no higher than 600 secs for several weeks) and making an IP change for a small business website on Monday, I took down the old web service just over 24 hours later on Tuesday evening. We then had reports of some customers not being able to access the website on Wednesday morning. On investigation using my iPhone it would appear that Apple Private Relay is still directing clients to the old IP address.

It's just as well I have iCloud+ as I would never have seen this issue otherwise and would have been none the wiser as to why some customers were having problems.

Has anyone else seen this and/or have a fix other than waiting longer? Do you know how long it takes for Apple Private Relay to update? This isn't expected behaviour of DNS?

I spoke to someone at Apple yesterday and there wasn't much they can do. I hope they're escalating internally as almost 3 days later it's still pointing users to the old IP address despite having ample time for proper DNS propagation.

Answered by JonathanMB in 867679022

This has now been resolved - despite being on an IPv4 only connection, Private Relay was using IPv6 where the DNS update had been overlooked.

tldr: make sure to update IPv6 DNS if you have that.

Up to around 96 hours since the DNS change and Apple Private Relay still directs browsers to the old server. What is going on?!

Accepted Answer

This has now been resolved - despite being on an IPv4 only connection, Private Relay was using IPv6 where the DNS update had been overlooked.

tldr: make sure to update IPv6 DNS if you have that.

DNS updates and Apple Private Relay - major issue
 
 
Q