Hello, I'm in the middle of migrating a client over. We're doing a test run with a spare domain name.
When I migrated my personal website over from WebFaction, I did not have to create any DNS A records. Everything worked and within a couple of hours of pointing my domain registrar over to the Opalstack name servers, my websites pop upped and the switch was done.
With my client, they decided to go for a VPS. I repointed the DNS servers on GoDaddy around 10 PM last night. I just checked at 6 AM this morning using various online DNS propogation tools and not a single server was showing the my client's new IP address for the domain in question.
It then occurred to me that perhaps, unlike the shared hosting, I needed to manually create the A records. So I did that, and within minutes they started to propagate and showing up on the DNS checkers.
So I'm thinking I misunderstood the Opalstack documentation on the DNS entries and that Opalstack only handles generating A records for the IP addresses automatically if it's a shared hosting account. For VPS instances, we have to create them manually. If that's correct, it may be worth updating your documentation accordingly.
Could someone confirm that this is the case?
Also, how does this impact setting up email records? I had no problems with shifting over email with shared hosting, but I seem to be having similar problems with the VPS. I'm worried that there is going to be a near-future moment where the mailbox on the old WebFaction system stops working and the replacing mailbox on the new Opalstack system isn't working. I set up the mailboxes, but smtp and imap tests are failing.
