New Symbiostock Hosting Guide

Working on this Symbio instruction below, but the registrar (GoDaddy) will only let you enter nameservers to point to, NOT ip address. States: “We can’t display your DNS information because your nameservers aren’t managed by us.” Those nameservers point to the hosting account (obviously). This is the way I’ve always done it. What am I missing here?

Symbio Instruction Lightsail: “Follow your registrar’s instructions on changing the DNS to point your domain to the public IP address from your Lightsail instance. Generally this means after you have registered the domain, you go to edit the domain’s DNS records in your registrar, and where you see their IP address, you change it to your Lightsail one.”

For all who it may help, I ended up setting up a DNS Zone in lightsail and used the 4 nameservers it gave me and entered those in godaddy. Then I created a Domain in that DNS Zone.
Also if you had any trouble configuring a username and password for your Plesk instance, try this:

Complete the following steps to configure a username and password for your Plesk instance, and sign in to the Plesk panel for the first time.

In the Instances tab of the Lightsail home page, choose the SSH quick connect icon for the Plesk instance that you want to set up (you may need to reboot it-more below-it should say “running” below it).

Connect to your Plesk on Amazon Lightsail instance
Enter the following command.

sudo plesk login | grep -v internal:8

One-time sign in for your Plesk instance.
IMPORTANT
If you recently attached a static IP to your Plesk instance, you might get a one-time login URL that uses the old public IP address. REBOOT the instance, and run the above command again to get a one-time login URL that uses the new static IP address.

Highlight the URL shown in the browser-based SSH window, then choose the clipboard icon, and copy the URL to your local clipboard.

The clipboard for the web-based SSH session.
Open a new browser window, and browse to the URL that you copied.

You might see a browser warning that your connection is not private, not secure, or that there’s a security risk. This happens because your Plesk instance does not yet have an SSL/TLS certified applied to it. The prompt may be different than what is shown in the following example depending on the browser you use.

Chrome warning for private connection.
Complete one of the following steps depending on the browser that you use:

Chrome — Choose Advanced, and then choose Proceed to continue to the Plesk set up page.

Edge — Choose Details, and then choose Go on to the webpage (Not recommended) to continue to the Plesk set up page.

Firefox — Choose Advanced, and then choose Accept the Risk and Continue to continue to the Plesk set up page.

Internet Explorer — Choose More information, and then choose Go on to the webpage (Not recommended) to continue to the Plesk set up page.

Enter your contact name, email address, and password.

In this page, you can change the default admin contact name if you prefer to use something different. However, that is only the display name; your username to sign in to Plesk will continue to be admin.

Hope this will help others.

All-in-One WP Migration works great for moving over an entire site from other hosting to Lightsail plesk