Could not route to /zones/undefined/dns_records/086dccd5079680bcb18284df4453f83f, perhaps your object identifier is invalid? No route for that URI.
What is the issue you’re encountering
I am attempting to set up a custom email domain on iCloud and getting an error message from Cloudflare.
What steps have you taken to resolve the issue?
I contacted Apple support, but they and I agree that it appears to be a problem with the Cloudflare system.
What feature, service or problem is this related to?
DNS records
What are the steps to reproduce the issue?
When attempting the set up in iCloud, after entering the domain name, it detects that the domain is with Cloudflare, then connects to the Cloudflare system to make the DNS changes. When attempting to finish the changes, I get the error below and it fails.
Could not route to /zones/undefined/dns_records/086dccd5079680bcb18284df4453f83f, perhaps your object identifier is invalid? No route for that URI.
I have the same issue and have escalated a case with the Apple Support engineering team. Based on what I see the zone is not being set in the API call to Cloudflare.
I’ve manually created the records within Cloudflare, but Apple will not verify/enable the required routing for mail. In the past prior to this integration I’ve always updated the DNS records using Terraform without a problem.
I’ve also gone down the path of updating the records manually and then manually calling the Apple callback endpoint and they still won’t verify the records.
Can you share your domain as well as the records that you need to add so I can check? It seems strange that there should be multiple problems at once, both with records creation as well as verification.
I have made the changes manually, but Apple still wants to make them again. It seems to be hung up on the dot at the end of the server names in the MX records. I had the trailing dots in there when I made the manual entries but I guess Cloudflare strips them off. Apple sees them missing and wants to make a change.
Had a call with Apple, went to demo them the problem and it only went and worked, not sure what went wrong but the main thing is its now up and running.