feat: add required ipv6 records for apex domains

[Tom Bojer (tombojer)]

No description provided.

[Renaud Hager (renaudhager)]

Since now we are doing an active check, I think it worth mentioning it and therefore they should plan accordingly the domain add in their application?

[Copilot]

Pull request overview

Adds IPv6 DNS guidance for apex custom domains in the Shopware PaaS CDN documentation, ensuring users configure both IPv4 and IPv6 records when pointing apex domains at Fastly.

Changes:

• Documented required AAAA records for apex domains (in addition to existing A records).
• Updated the “Managing Custom Domains” deployment guidance to mention additional CLI deployment options.
• Added basic troubleshooting guidance for domain creation/DNS issues.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

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]

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]

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**.