Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm starting a gradual process of moving from one VPS on one ISP to another VPS on another ISP and I have some questions about DNS settings.

The long term goal is to eventually be completely shut of the old ISP.

The new VPS is running Plesk, which automatically sets up nameservers and DNS entries when the domain is created through the panel.

The thing is, it sets up what seems to be a ridiculous number of entries when the domain is created:

Header - Record Type - Value

  • {I.P Address / Mask } - PTR - domainname.suffix.
  • ftp.domainname.suffix. - CNAME - domainname.suffix.
  • ipv4.domainname.suffix. - A - I.P. Address
  • lists.domainname.suffix. - CNAME - domainname.suffix.
  • mail.domainname.suffix. - A I.P. Address.
  • mssql.domainname.suffix. - A - I.P.Address.
  • domainname.suffix. - NS - ns.domainname.suffix.
  • domainname.suffix. - NS - ns1.domainname.suffix.
  • domainname.suffix. - A - I.P. Address.
  • domainname.suffix - MX(10) - mail.domainname.suffix.
  • ns.domainname.suffix - A - I.P. Address.
  • ns1.domainname.suffix - A - I.P. Address.
  • sitebuilder.domainname.suffix - A - I.P. Address.
  • webmail.ddomainname.suffix - A - I.P. Address.
  • www.domainname.suffix - CNAME - domainname.suffix.

The thing is, this really is going to be a gradual process. We have an FTP site which will continue to be hosted on the old server - it's been there for years and sorting out the various usernames/passwords and access rights to it is going to be a nightmare.

The old ISP will continue to manage the company emails, so I really don't want to be messing around with the existing MX records.

Looking at the existing DNS zone records on the old ISP, I have the following entries.

Host - Type - Priority - Destination / Data

  • domainname.suffix. - A - 0.domainname.suffix. - I.P. Address
  • domainname.suffix. - MX - 10.domainname.suffix. - pxy.a.mx.ISP's Domainname.suffix
  • domainname.suffix. - MX - 20.domainname.suffix. - pxy.b.mx.ISP's Domainname.suffix
  • domainname.suffix. - NS - 0.domainname.suffix. - ns.ISP's DomainServer.suffix
  • domainname.suffix. - NS - 0.domainname.suffix. - ns1.ISP's DomainServer.suffix
  • www.domainname.suffix - A - 0.domainname.suffix. - I.P. Address

I'm aware that Priority generally isn't presented as it is above, however thats how the ISP shows it.

So looking at these, I'm wondering what my best way to proceed is.

If I create the domain as normal in Plesk, I can then edit and remove the values I don't need, so they continue to point to the places they should, correct?

What I'm looking at doing here is ending up with the following, in Plesk:

Header - Record Type - Value

  • {I.P Address / Mask } - PTR - domainname.suffix.
  • ipv4.domainname.suffix. - A - I.P. Address
  • domainname.suffix. - MX(10) - pxy.a.mx.ISP's Domainname.suffix
  • domainname.suffix. - MX(20) - pxy.b.mx.ISP's Domainname.suffix
  • domainname.suffix. - NS - ns.domainname.suffix.
  • domainname.suffix. - NS - ns1.domainname.suffix.
  • domainname.suffix. - A - I.P. Address.
  • www.domainname.suffix - CNAME - domainname.suffix.

Doing that obviously means removing the corresponding entries on the old ISP zone file, but my problem then becomes, how do I manage the FTP entry?

Can I simply create an ftp.domainname.suffix entry on the new site and enter the IP address of the old server as the value? What else would I need to set out there? Most importantly, have I missed anything?

share|improve this question
    
How many domains are you moving? –  jeffatrackaid Nov 20 '12 at 15:27
    
@jeffatrackaid Just the one, but we are moving from a bit of a nanny state ISP to a less interfering one. –  inksmithy Nov 22 '12 at 9:31

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.