It seems there's a conflict due to two A records for the '@' host. In order to
resolve this, you will need to access your GoDaddy domain settings and make sure
only one A record exists for your custom domain that points to your Google
Compute Engine VM's fixed IP. Please follow these steps: 1. Log in to your
GoDaddy account and go to your DNS settings page for the domain in question. 2.
Look for the A record with "WebsiteBuilder Site" and see if there is an option
to deactivate or remove the Website Builder or any other conflicting services
that GoDaddy may have added. 3. If your domain is locked, find the domain
settings where you have the option to unlock the domain. This is typically a
safety feature by domain registrars to prevent unauthorized changes. 4. After
unlocking the domain, if you are not able to delete or edit the conflicting A
record, you should create a support ticket with GoDaddy or get in touch with
their customer service to assist you in cleaning up your DNS records. 5. As an
alternative, you can also consider creating a subdomain (like
appsmith.yourdomain.com) and create an A record for that subdomain pointing to
your VM's IP address. This can sometimes be a simpler solution as it often
doesn't conflict with existing services like a root domain (@) record might.
Remember that after any DNS changes, it can take some time for changes to
propagate around the internet (typically up to 48 hours). If you have just made
the changes, you may need to wait a bit longer or flush your DNS cache. If you
continue to face issues, please contact GoDaddy support for domain-specific
assistance as they will be able to help you remove any undesired records and
ensure the DNS setup is correct. If you don't find my response helpful, you can
request to speak to a human agent