Results 1 to 4 of 4
  1. #1
    Join Date
    Oct 2005
    Location
    Widnes, England
    Posts
    593

    Moving from reseller to VPS

    Hello,

    I've bought a VPS and have copied all of the clients data to the new server. I've setup my resolvers to point to the new nameserver IPs.

    Now I need to edit the host.com host record IPs from my old ones to my new ones. (example domain) ns1.host.com and ns2.hosting.com

    I've gone to fasthosts' control panel where I registered host.com and attempted to delete the old host records but this fails because other domains are pointing to the current records.

    How can I update the host records for ns1 and ns2 with my new nameserver IPs?
    Sean

  2. #2
    Join Date
    Mar 2008
    Location
    kolkata, India
    Posts
    102
    HOW-TO : Setting up Nameservers in cpanel.

    Special Notes:
    Some version of WHM/CPanel come with broken NDC. To fix this:

    SSH into your box as root.

    (a) Type: cd /scripts
    (b) Type: ./updatenow
    (c) Type: ./fixndc
    (d) Type: service named stop
    (e) Type: service named start

    ********************************************

    1. Setup Nameservers In WHM
    Go into WHM (Web Host Manager) and select Edit Setup from the Server Setup menu on the left. Enter ns1.newdomain.com in the Primary Nameserver field. Hit 'Assign IP Address' (write the IP down or remember it for the next step). Then hit 'Add an A Entry for this nameserver'.

    Repeat this process for the Secondary Nameserver field.


    2. Register Nameservers
    Go to your domain registrar and register ns1.yourdomain.com (111.111.111.111) and ns2.yourdomain.com (222.222.222.222) as nameservers. 111.111.111.111 being the primary nameserver IP from step 1 and 222.222.222.222 being the secondary.

    These registrations may take a few days to propagate (often as many as 3 days).


    3. Reverse DNS
    You may need Burstnet to enter a reverse DNS pointer (PTR Record) for your nameservers. You'll need to let them know each nameserver and its IP address. Sometimes you can suffer non-delivery of mail if you don't so this. Reverse DNS pointers can take a while to propagate. Send an email to [email protected] with the following...

    To: [email protected]
    From: <Your Address>
    Subject: PTR Request

    Please create the following PTR records.
    123.123.123.123 - server.mydomain.com (Main Server IP)
    111.111.111.111 - ns1.mydomain.com (This of course being your info)
    222.222.222.222 - ns2.mydomain.com


    4. Tidy Up Junk Nameservers
    Go into WHM (Web Host Manager) and select Manage Nameserver IPs from the Server Setup menu on the left. Remove any nameservers you don't recognise. This is just a tidy up exercise in case anyone's set anything up on the box before you.


    5. Initial Nameserver Setup
    Go into WHM (Web Host Manager) and select Initial NameServer Setup from the Server Setup menu on the left.


    6. Restart BIND
    Restart BIND from SSH with (step 5 restarts BIND, but sometimes needs a proper stop and start for it to work):

    service named stop
    service named start


    7. Manual Checks
    This process doesn't always work, so there are some things you can check manually via SSH.

    pico /etc/wwwacct.conf
    Check that the nameservers are correctly specified on NS1, NS2 etc.

    pico /etc/resolv.conf
    Check that there are nameserver entries for each IP. There may also be one for 127.0.0.1 - this is okay.

    Should read as follows:

    domain maindomain.com
    search maindomain.com
    nameserver 127.0.0.1
    nameserver 111.111.111.111
    nameserver 222.222.222.222

    Where 'maindomain.com' is the main domain of my server, and '111.111.111.111' and '222.222.222.222' are the IP addresses of my primary and secondary nameservers.


    pico /etc/nameserverips
    Check that there are entries for each IP acting as a nameserver.

    ********************************************

    That should be it...
    Sysfirm
    So you think your server is secure?
    Try our security Service
    With SysFirm

  3. #3
    Join Date
    Oct 2005
    Location
    Widnes, England
    Posts
    593
    Hello,

    I'm trying to do step 1 but I get "Sorry, the nameserver ns1.mydomain.com already has the ip 77.74.195.181 assigned to it."

    I've tried going to fasthost (where I registered the domain) and delete the current host records but it wouldn't let me. Fasthost support says it's because domains are pointing to the nameservers. Surely companies have moved servers without getting customers to mess around with where there domains are pointing to.
    Sean

  4. #4
    I'm trying to do step 1 but I get "Sorry, the nameserver ns1.mydomain.com already has the ip 77.74.195.181 assigned to it."

    Go to the Name Server IP's area in WHM, and delete the old ones. You may have to go into Tweak Settings, and check the "Disable Whois Lookup" option towards the bottom.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •