I have a system which is dialup because it is out in the boonies. It has a static IP address which the ISP tells me will become DHCP around the end of the month (presumably 01 Dec 2009). Since it has a domain name which has been around since uunet days, I am loathe to drop it ....

I have set up a linode server as a mail server, tested it, it appears to be working. I want to switch the domain name to the linode account.

I see three organizations involved in this mess. My domain name registrar points to the ISP. The ISP has the DNS records which point to the current static IP address which will soon become defunct due to becoming DHCP. And Linode hosts the new server which I want DNS to point to, both as domain and primary MX.

I could tell the registrar to switch DNS records and set up the Linode DNS. But the ISP still has records of my domain, and even if they aren't recognized by the rest of the world because the registrar will point them to Linode,anyone using the ISP's domain server just might get the old defunct address.
It seems to me the simplest solution is to get the ISP to change, but they might get obstreperous about pointing to someone else's server.

What is the proper thing to do here?

This is your answer, but reverse the order: set up linode DNS first, then switch the registrar to point at linode DNS servers.


Nobody should query your ISP's domain server once your registrar changes have propagated, not even your ISP. Worst-case you just need to ask your ISP to remove your old DNS entries.

That is more or less what I have done -- set up Linode DNS. But since my mail server is on the blink, I can't receive email until I get mail service via Linode, and the registrar has not responded yet via alternate email. It would be a big help if my ISP would repoint their DNS, but they haven't responded yet either.

And the big T-week holiday is coming. This does not bode well ...