Migrating in from self-hosting at AWS

  • Unknown's avatar
    dublevay · Member ·

    Hello – in the early hours of this morning I migrated my existing WordPress site across to WordPress.com from self-hosting at AWS. The migration completed successfully, and I replaced the Nameserver settings at my domain registrar with WordPress NS1, 2 & 3 servers.

    That seems to have worked OK, but I am confused as to what exactly I should be selecting as my Primary Domain. If I select dragonpluselectronics.wpcomstaging.com, I can connect to the website, but only using the wpcomstaging address. If I select my primary domain as http://www.dragonplus-electronics.co.uk, then it still connects back to my existing AWS site. I know these things can take a little while, but as I am unsure as to what should actually be the primary domain, I could just be wasting time waiting for the wrong thing to be actioned.
    I don’t know how to look at the actual IP addresses that the WordPress nameservers are referencing, to understand whether my selection of the http://www.dragonplus-electronics.co.uk domain is actually purposely selecting my old website? It would be so good if there were a little more detail on the domain selection page, which would indicate the intended destination IP address.

    The blog I need help with is: (visible only to logged in users)

  • Unknown's avatar
    aisajib · Member ·

    Hi there!

    Welcome to WordPress.com! I’ll be happy to help you with your questions!

    It appears you have a total of two custom domains on your WordPress.com site. dragonpluselectronics.com is registered with us, and dragonplus-electronics.co.uk is connected via Domain Connection.

    I checked and found that dragonplus-electronics.co.uk is currently pointing to your WordPress.com site. What happens when you visit this domain now? If you’re being redirected to dragonpluselectronics.com, that means the DNS propagation is complete, and you can make dragonplus-electronics.co.uk the primary address on your site.

    If you still see the old AWS-hosted site, it means you’ll need to wait a while longer, as DNS changes can take up to 72 hours to take effect.

    Hope that helps! Feel free to let us know if you have more questions.

  • The topic ‘Migrating in from self-hosting at AWS’ is closed to new replies.