On Mon, 14 Mar 2022 at 19:17, mick mbm@rlogin.net wrote:
First point, do you actually /need/ to transfer the domain?
Need is a strong word. But I have domains across a couple of registrars which have various flaws I wanted to get past. A lot of the domains are non-critical so I'm moving them first but using them as a test of procedure.
https://baldric.net/2009/08/02/dns-failure-a-cautionary-tale/
Those issues all sound familiar!
Second point. Do you actually /need/ to add new A (or any other) records to the domain immediately ater the transfer? If so, why not add the records now (with a long TTL) and then transfer? That way it would not matter over much if there were a delay.
The issue is that (at present) I'm using the DNS provided by the registrar. So the DNS records are all correct in the old registrar's DNS, but they will be deleted at some point after I move to the new one. So the records need migrating to the new host.
There is an obvious workaround: use a separate DNS. And this is something I have considered and will probably do at least for domains that matter. But for some domains, it's easier to use the provider's DNS because they also use basic functions from that provider such as web or email forwarding, which generally assume if not require that the DNS is set to use their own servers.
Moreover, this is really about filling a hole in my understanding of how DNS works.