Michael Masin wrote:[...]
The email service won't be activated until the zone file is configured toHow are you supposed to gracefully migrate a live domain?
Tucow's specification (inbound.domainname.tld.emailmx.com. as the *only* MX
record, mail CNAME correct, etc.) Any deviation will prevent activation.
in every successful migration of any sort that I've ever done, the only reliable method has been to keep both the old and new services running simultaneously for a brief period, at least 24 hours above your TTL (to accommodate ISPs that don't grasp how TTLs work)
Exactly. And right now this situation is falling on its face and failing my customer.
- Authoritive nameservers changed almost 18 hours ago.
- inbound.domain.tld.emailmx.com set as the *only* MX record 6 hours ago.
- accounts are still not activated and showing "Verifying MX record" in the RWI. The authoritive nameservers are showing proper MX info on a dig query. If the authoritive nameservers are giving the right info, who then is it querying to verify?
The way this is set up is not appropriate for the real world, and as Dave pointed out, especially for trying to migrate a live domain.
The verification should check only that inbound.domain.tld.emailmx.com simply is ONE of the MX's for the domain or perhaps even the primary MX. This really needs to be changed ASAP, please.
Thanks, Todd
