We’ve noticed that when you create a new zone, with option to import existing DNS, there’s a delay on the importing of those DNS records. The delay is not consistent, and can be anywhere from 2-60 seconds.
This creates a problem, because if we want to create a zone, then add DNS records, we have no way of knowing WHEN to add dns records, as we only want to add after import is done.
I really feel the import of DNS records should at least have an option to be synchronous, because the async method is just causing problems in a standard processing. I’d much rather wait for completion of zone creation than get a half-baked zone creation.
Furthermore, results seem inconsistent, but it appears that when we add records BEFORE you are done importing, NOTHING gets imported. I’m guessing maybe your import hits an error on “existing record” and drops out of its loop?
This really could all be solved by making the import of dns records synchronous and is far more appropriate logic. If a person wants the old behavior, they can choose NOT to import the dns records, and later trigger command to import them if they want.
The async behavior though is really illogical and introduces too many odd behaviors.