Migrating DNS domains/records from VPS.NET to Linode
Unfortunately while Linode does support DNS zone transfers, VPS.NET does not… but luckily both have APIs which allow this among other things. So I have quickly put together a ruby script, and got all my domains migrated in a very short time.
However, I have a doubt: because, while importing, Linode API did not support the value "@" used by VPS.NET to define the default value for a host, I have omitted the "host" parameter when creating domain resources with Linode API having that value as host. The parameter in fact is optional, so I guess that omitting it would make the API set the correct default value, but now in Linode DNS manager I see something like this:
Is this correct or should it show something other than an empty string?
I want to double check before chaging name servers for these domains.
Also, if you want to make sure everything is OK on linode's nameservers before moving over, use the dig command:
$ dig hoopycat.com @ns1.linode.com (...) ;; QUESTION SECTION: ;hoopycat.com. IN A ;; ANSWER SECTION: hoopycat.com. 86400 IN A 126.96.36.199 (...)
$ dig hoopycat.com mx @ns1.linode.com (...) ;; QUESTION SECTION: ;hoopycat.com. IN MX ;; ANSWER SECTION: hoopycat.com. 86400 IN MX 10 mail.hoopycat.com. (...)
Also check @ns2.linode.com, ns3, ns4, and ns5 to make sure those are well too.
Am happy to see that Linode have DNS service in London too!
Query time is great, so I have set ns5.linode.com as the main name server, followed by Neward/NS4 (which if I remember rightly still is the best option for Europe, among the other data centres), and then the others.
A smart resolver will tend towards preferring the best-performing of the available nameservers, so stick all five in there.