Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs] GoDaddy Redirection #289

Merged
merged 2 commits into from
Oct 29, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
23 changes: 22 additions & 1 deletion doc/user-guide/custom-domains.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,27 @@ Some DNS providers don't support `ALIAS` records. If that's your case, you might
need assistance, [contact us](mailto:[email protected])
```

(godaddy-redirect)=
### GoDaddy Redirection

Since GoDaddy doesn't support Alias, as well as a non-IP for the CNAME root domain, you will need to configure a subdomain with www.yourdomain.com and redirect the traffic from your top domain (`yourdomain.com`) to it. To do so:

1. Create a `www` [custom subdomain](custom-subdomain).
2. Update your DNS according to the instructions for this new subdomain `www.yourdomain.com`.
3. Set up a Forwarding Rule to your Subdomain, of type `Permanent (301)` redirect.

![1-forwarding-rule](../static/custom-domains/godaddy_redirect_1.png)
![2-forwarding-rule](../static/custom-domains/godaddy_redirect_2.png)

```{important}
For this to work, make sure to generate a new **subdomain** for your `www.yourdomain.com`, since the SSL certificate generated for the top domain doesn't cover the www subdomain in case of a redirect.
```

So when looking at the current domain configured for your application, you should see `www.yourdomain.com` and not `yourdomain.com`, as seen below:

![3-forwarding-rule](../static/custom-domains/godaddy_redirect_3.png)


(custom-subdomain)=
## Adding a custom subdomain

Expand Down Expand Up @@ -205,4 +226,4 @@ Flag: 0
Tag: issuewild
CA domain: "amazon.com"
TTL: 60
```
```
Loading