Domain – point a domain name to the server, without changing any MX Records etc – do I change the A Records, the NS Records, or both

a-recorddomaindomain-name-systemns-record

My client has a domain name clientsdomain.com, with DNS records set out as such:

Lookup has started…

Trying "clientsdomain.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21301
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 3

;; QUESTION SECTION:
;clientsdomain.com. IN  ANY

;; ANSWER SECTION:
clientsdomain.com. 10800    IN  NS  ns2.their-current-webhost.co.uk.
clientsdomain.com. 10800    IN  NS  ns.their-current-webhost.co.uk.
clientsdomain.com. 10800    IN  SOA ns.their-current-webhost.co.uk. hostmaster.their-current-webhost.com. 2012111658 86400 604800 2419200 10800
clientsdomain.com. 10800    IN  A   9.170.40.230
clientsdomain.com. 10800    IN  MX  10 site2.smtp.exch500.their-current-webhost.net.

;; ADDITIONAL SECTION:
ns.their-current-webhost.co.uk. 4176    IN  A   9.170.40.2
ns2.their-current-webhost.co.uk. 3984   IN  A   9.170.43.3
site2.smtp.exch500.their-current-webhost.net. 55681 IN A    05.217.20.189

Received 270 bytes from 192.168.1.2#53 in 54 ms

I've changed IP addresses and some domains for the sake of privacy. Here's what I want to do:

  • I want to point their domain to our web host, at MediaTemple
  • MediaTemple's IP Address is 205.186.175.173
  • MediaTemple's Nameservers are ns1.mediatemple.net and ns2.mediatemple.net
  • I don't want to interfere with any MX Records or email setups – their emails need to keep functioning

So my question is, do I need to get them to change their NS Records, or their A records, or both?. Do they need to just change the A-records and remove the NS Records which reference their old web host? Or vice-versa?

Thanks!

Best Answer

In an ideal world, they'll just need to change the A records and be done with it.

The issue may come when they cancel their existing hosting as this may take their current nameservers with it. What I typically do to transfer a domain without affecting site or e-mail uptime is as follows:

  1. Change the A record to point to the new hosting. Remember to change both domain.com and www.domain.com if this is applicable.
  2. Ensure the above is fully working.
  3. Add the domain and replicate all of the existing records on your own DNS server (except NS records, which should be your own).
  4. Change the nameservers of the domain to point to your DNS server.

Remember that the NS records listed by dig are actually being served up by the domain's current DNS server. When you 'change the nameservers for a domain' this is done in the control panel of the domain registrar and will appear in the domain's whois information.

Related Topic