Skip to content

feat: add required ipv6 records for apex domains #2114

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.

Sign up for GitHub

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

Open
Tom Bojer (tombojer) wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: add required ipv6 records for apex domains #2114

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
16 changes: 15 additions & 1 deletion products/paas/shopware/cdn/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,10 +57,24 @@ Configure a `A` with your custom domain's DNS to point to:
151.101.195.52
```

and `AAAA` records to point to:
Copy link

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The paragraph starting with "and AAAA records to point to:" reads like a continuation of the previous sentence but is a new paragraph in Markdown; starting a paragraph with "and" is grammatically awkward. Consider rephrasing to a full instruction like "Configure AAAA records (IPv6) to point to:" (and optionally mirror the wording used for the A record section).

Suggested change
and `AAAA` records to point to:
Configure `AAAA` records with your custom domain's DNS to point to:

Copilot uses AI. Check for mistakes.

```dns
2a04:4e42::820
2a04:4e42:200::820
2a04:4e42:400::820
2a04:4e42:600::820
```

This configuration ensures that all traffic to your custom domain is routed through the Fastly CDN for optimal performance and caching.

#### Managing Custom Domains

Custom domain management is handled through the `sw-paas` CLI domain command. You can attach multiple domains to a single shop. Following domain creation, you must update the application using `sw-paas application update`. You may use the same commit to trigger a deployment. This process will be automated in future releases.
Custom domain management is handled through the `sw-paas` CLI domain command. You can attach multiple domains to a single shop. Following domain creation, you must create an application deployment using `sw-paas application update` or just `sw-paas application deploy create`. You may use the same commit to trigger a deployment.
Copy link

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This suggests using sw-paas application update to (re)deploy after domain creation, but sw-paas application update typically requires providing a commit SHA and is primarily an update/build-and-deploy workflow. To avoid confusing readers, either (1) recommend sw-paas application deploy create consistently here, or (2) explicitly mention the commit SHA requirement and clarify when to use update vs deploy create.

Suggested change
Custom domain management is handled through the `sw-paas` CLI domain command. You can attach multiple domains to a single shop. Following domain creation, you must create an application deployment using `sw-paas application update` or just `sw-paas application deploy create`. You may use the same commit to trigger a deployment.
Custom domain management is handled through the `sw-paas` CLI domain command. You can attach multiple domains to a single shop. Following domain creation, you must create an application deployment using `sw-paas application deploy create`. You may use the same commit to trigger a deployment.

Copilot uses AI. Check for mistakes.

Subsequently, you can configure the domain within Shopware and associate it with a storefront. Status update functionality is currently under development.

If you encounter an error during the domain creation process, a possible solution is to check the domain's DNS configuration.
Ensure that the DNS records are correctly set up according to the guidelines provided above.
Additionally, verify that there are no typos in the domain name and that the ***DNS changes have propagated successfully***.
Copy link

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The emphasis markup ***DNS changes have propagated successfully*** (bold+italic) is not used elsewhere in these docs and can look inconsistent in rendering. Consider switching to the standard **...** emphasis used throughout the Shopware docs, or removing emphasis entirely if it’s not meant to be extra-strong.

Suggested change
Additionally, verify that there are no typos in the domain name and that the ***DNS changes have propagated successfully***.
Additionally, verify that there are no typos in the domain name and that the **DNS changes have propagated successfully**.

Copilot uses AI. Check for mistakes.
If issues persist, consider reaching out to support for further assistance.