Custom Domains: Waiting for DNS and Clearer Certificate Errors

What's changed

• Static Sites, Managed Apps and Storage Share: a verified domain whose DNS record is not published yet now shows Waiting for DNS. While your DNS provider's own nameservers say the record does not exist, the certificate is not requested, so it does not start while resolvers still answer not found. If we cannot get an answer from those nameservers, the domain is connected as before. We look again every minute on the first day and hourly after that, connect the domain ourselves, and you do not need to click Verify again. A domain still waiting after seven days is connected anyway
• Static Sites, Managed Apps and Storage Share: if a first certificate takes longer than ten minutes because the domain does not resolve yet, the domain now says so and explains that resolvers can keep an earlier not-found answer for up to an hour. A failed DNS lookup is described in plain words instead of showing the resolver's raw message
• Rapids: a TXT record at _acme-challenge.your-domain, next to the CNAME the console shows as the certificate record, stops the certificate from being issued. Check this record in the domain drawer now names that TXT record and tells you to delete it and keep only the CNAME, the domain shows Waiting for DNS with the same message, and the certificate error names the record instead of asking you to check records that were right
• After you fix the record, automatic certificate retries can still be up to 32 hours apart; contact support to have the certificate requested straight away
• On a root domain whose public addresses match your product's hostname, the domain drawer now shows a neutral DNS addresses match note instead of asking you to replace a record. Public DNS cannot show whether your provider uses an ALIAS, ANAME or flattened CNAME, or fixed A and AAAA records, so check the record type at your provider. This applies to Static Sites, Rapids, Managed Apps and Storage Share domains