The TTL has been set to 1H, so that IP changes for example.com can be made more quickly.
The registrar has been configured with ns1.example.com and ns2.example.com, verified using WHOIS lookup. ns1 and ns2 are based in Texas.
We're moving all of our stuff to New Jersey, because the new owner thinks it's a good idea.
So, we routed A records example.com, www.example.com, etc to New Jersey now, and that leaves ns1 and ns2 which are still based in Texas.
So, we set up new nameservers in New Jersey ns3.example.com, and ns4.example.com, and they are working well, but at this point the registrar/WHOIS is still set up to direct users to continue using ns1 and ns2.
I've been told that a 48-hour update is required for the WHOIS nameserver updates to take effect, so the logical course is to list the New Jersey DNS servers (ns3.example.com and ns4.example.com) on the WHOIS, then wait at least 48 hours before shutting down the Texas servers (ns1.example.com and ns2.example.com).
But, since the TTL is set to 1H, do I still need to wait 48 hours? Will public/recursive/ISP DNS servers cache the Registar/WHOIS nameserver list for longer than the TTL of the A records?
(I am not concerned about systems that ignore the TTL entirely, I'm only asking whether those that respect A record TTL will also use that same TTL for the Registar/WHOIS nameserver list)