John_Smith3 reports that while www.mydomain.com successfully directs to their Discourse site, mydomain.com (without www) does not, despite following GoDaddy setup instructions. endukugga clarifies this is a DNS issue: the www subdomain likely has an A record pointing to the Discourse server IP, but the root domain (@) does not. They suggest checking GoDaddy’s DNS settings or seeking help from others familiar with it. merefield adds that if using HTTPS (recommended), Let’s Encrypt and proxy configurations must also be addressed, and links to a guide on multi-domain Let’s Encrypt setup; they advise simplifying by using only one domain. RGJ offers a solution: configure the @ record as an A record pointing to 45.55.96.103, which leverages a free service that redirects any subdomain (including root) to www.anything.tld, effectively solving the issue.
This issue has nothing to do with Discourse and it’s about your domain DNS records. From your description it looks like you have an A record for the subdomain www pointing at the IP address where you’re hosting Discourse, which is different to the root domain (usually an A record with the name @). I’ve never used GoDaddy, so it’s better if you browse through their help section unless somebody else here can help you out.