Skip to main content

Site timing out, after server migration

jasoncollege24
Domain: REDACTED.com Old server OS: CentOS7 New server OS: Ubuntu 20.04 WHM Access? Yes (on both servers) Relevant Details: old nameserver selection: Bind new nameserver selection: PowerDNS ("Bind is not available for your system. Please choose another nameserver configuration.") Steps taken: 1. Install Ubuntu/cPanel 2. Login to new WHM, and change settings to match old server. 3. Update nameservers in WHM on new server, assigning them to the new local nameserver IPs. 4. Transfer my cPanel account to new server, using the transfer tool in WHM 5. verify account transfer on new server 6. change hostname in WHM (new server) 7. update DNS zones to all have the correct nameservers 8. Change IP of website to secondary IP, leaving hostname on a dedicated IP (same as old server) 9. change IP of nameservers at domain registrar to match the new server's nameserver IPs. (more than 12 hours ago) Last night, the domain pointed to the old server. Now it just times out completely. When using dig on the domain's IP, it times out on port 53. when doing dig on the domain name, or the domain name at the hostname's IP address it comes back giving me all the correct information. This all happens with or without the firewall enabled. FTP, WHM, and cPanel all work on the hostname's IP address, and WHM changes the URL to cpanel's default domain (cprapid.com) In the interface to change a website's IP address, when choosing an IP, the hostname's nameserver shows as cpanel's default nameserver. Everywhere else in whm and cpanel, NS1 points to my nameserver. Some questions: 1. Is there a way for me to find out why Bind is not available for my server? 2. Could this timeout issue just be DNS propagation at work? 3. if not, what can I do to track down the issue? Part of me suspects it might be the different nameserver selection, but I'm no expert. Any help would be appreciated.

Comments

4 comments

Date Votes
  • quietFinn
    8. Change IP of website to secondary IP, leaving hostname on a dedicated IP (same as old server)

    Seems that connections to that secondary IP do not work, don't know why. If you set domain to point to the primary IP it should work.
    0
  • jasoncollege24
    Seems that connections to that secondary IP do not work, don't know why. If you set domain to point to the primary IP it should work.

    This worked, but I'm concerned about the connection problem with the second IP address. I might have to check with my server provider. Thanks for the help.
    0
  • SimpleSonic
    This worked, but I'm concerned about the connection problem with the second IP address. I might have to check with my server provider. Thanks for the help.

    Having your server provider check your configuration would be your best option as we can only speculate possible issues without having root access to actually see your configuration.
    0
  • yalinyalniz
    Possible to wrong network settings on second IP but I agree with @ResellerWiz to server get checked.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post