You own learnaurelle.com, learnaurelle.org and
tradingdesk.me. This is how to make them behave like one website.
learnaurelle.com is the real site. Everything lives here.
www.learnaurelle.com works too.learnaurelle.org redirects to the .com, keeping the path.tradingdesk.me redirects to the .com as well
(or keeps serving the site — your call, see section 6).Pick one canonical address and send everything else there. Two domains serving identical content splits your search ranking and means every link, email and bookmark disagrees about what your school is called.
Measured directly against Cloudflare's resolver, not guessed:
| Domain | Nameservers | Apex record | Verdict | |
|---|---|---|---|---|
learnaurelle.com | Cloudflare marty / josephine |
A → 74.208.236.19AAAA → 2607:f1c0:100f:f000::200(both IONOS) |
IONOS MX + SPF | Zone ready, leftovers must go |
learnaurelle.org | Cloudflare nick / betty |
AAAA → 2607:f1c0:100f:f000::200no A record |
IONOS MX + SPF | Zone ready, leftover AAAA |
tradingdesk.me | Cloudflare josephine / marty |
Worker (proxied) | IONOS MX + SPF | Live and serving |
2607:f1c0:100f:f000::200 is the identical IONOS IPv6 address that broke
tradingdesk.me. Windows prefers IPv6 whenever both exist, so even after you attach
the Worker, that record would quietly send every visitor to an IONOS parking page while the
correct IPv4 record sits unused. It is present on both new domains. Delete it
first — step 2 — and you skip the whole problem.
CAA record, so nothing will block certificate issuance. And both
are already delegated to Cloudflare, so there is no nameserver change to wait on.
learnaurelle.comCloudflare dashboard → learnaurelle.com → DNS → Records. Delete exactly two rows:
| Type | Name | Content | Action |
|---|---|---|---|
| A | learnaurelle.com | 74.208.236.19 | Delete |
| AAAA | learnaurelle.com | 2607:f1c0:100f:f000::200 | Delete |
learnaurelle.orgSame place, one row:
| Type | Name | Content | Action |
|---|---|---|---|
| AAAA | learnaurelle.org | 2607:f1c0:100f:f000::200 | Delete |
MX → mx00.ionos.com, MX → mx01.ionos.com,
TXT → "v=spf1 include:_spf-us.ionos.com ~all", and any
_dmarc / autodiscover / _domainconnect entries.
Deleting an MX record stops mail to that domain within minutes and bounced mail does not come back.
learnaurelle.com at the appWorkers & Pages is account-level — click the Cloudflare logo at the top left
first, or go straight to
https://dash.cloudflare.com/?to=/:account/workers-and-pages.
Then tradingdesk → Settings → Domains & Routes → Add → Custom Domain. Do this twice:
learnaurelle.comwww.learnaurelle.comCloudflare creates the DNS records and issues the certificate itself. Expect it to be live in a minute or two.
The Worker is still named tradingdesk
internally. Workers cannot be renamed, and it makes no difference — visitors only ever see the
custom domain. Leave it.
For each of learnaurelle.com, learnaurelle.org and
tradingdesk.me:
These are per-domain settings. Setting them on one zone does nothing for the other two — a mistake that is easy to make and hard to spot.
Turning on Always Use HTTPS also keeps the redirect rules below simple, because they
then only ever have to match https://.
learnaurelle.org to the .comA redirect needs two pieces: a DNS record so Cloudflare receives the request at all, and a rule that tells it where to send the visitor.
learnaurelle.org → DNS → Records → Add record, twice:
| Type | Name | IPv4 address | Proxy status |
|---|---|---|---|
| A | @ | 192.0.2.1 | Proxied (orange cloud) |
| A | www | 192.0.2.1 | Proxied (orange cloud) |
192.0.2.1 is a reserved documentation address that intentionally goes nowhere. No
traffic ever reaches it — the request stops at Cloudflare's edge, where the redirect fires. The
orange cloud is what matters; a grey-cloud record would send visitors to a dead address.
learnaurelle.org → Rules → Redirect Rules → Create rule.
org to comhttps://*learnaurelle.org/*https://learnaurelle.com/${2}301 — permanentThe two * characters are numbered in order. ${1} is whatever precedes
learnaurelle.org, which catches both the bare domain and www. in a single
rule. ${2} is the path, so learnaurelle.org/algebra-1 lands on
learnaurelle.com/algebra-1 rather than dumping everyone on the homepage.
Single Redirects are free, with a limit of 10 rules per domain. You are using one.
tradingdesk.meTwo reasonable choices. Redirecting is the tidier one.
| Redirect it (recommended) | Keep it serving | |
|---|---|---|
| Result | Visitors land on learnaurelle.com |
Two addresses serve the same app |
| Why | One canonical name; old links keep working | The trading programme keeps its own identity |
| Cost | Nothing — you still own the name | Split search ranking, two sets of links |
The Worker is already attached to tradingdesk.me, and that is fine — a redirect rule
still fires. Cloudflare's own documentation is explicit that requests handled by Workers
do not suppress modern Rules, and Single Redirects run first in the pipeline, before the
Worker is ever invoked.
So you do not need to detach anything. Just add the rule:
tradingdesk.me → Rules → Redirect Rules → Create rule:
me to comhttps://*tradingdesk.me/*https://learnaurelle.com/${2}301, preserve query string onlearnaurelle.com is confirmed working. If you redirect
tradingdesk.me while the .com is still broken, you have no working
address left and no easy way to check your own site.
Supabase → Authentication → URL Configuration.
https://learnaurelle.com.
This is the single address injected into confirmation and password-reset emails.https://learnaurelle.com/**https://www.learnaurelle.com/**https://tradingdesk.me/** and
https://www.tradingdesk.me/**http://localhost:8080/** for local testingDo this after learnaurelle.com loads, not before. Getting the Site
URL wrong makes password resets fail silently — the email arrives, the link looks right,
and it simply does not work.
Listing an address that is not live yet is harmless, so the redirect list can be filled in early. Only the Site URL needs to wait.
https://learnaurelle.com → the app, with a padlock.https://www.learnaurelle.com → the same.https://learnaurelle.org/login.html → should land on
https://learnaurelle.com/login.html, path intact. If it lands on the homepage
instead, your target URL is missing ${2}.http://learnaurelle.org (plain http) → still redirects, thanks to
Always Use HTTPS.learnaurelle.com.If a redirect does not fire, open Rules → Trace, enter the URL, and Cloudflare will tell you which rule matched.
301 is cached hard by browsers — once Edge has learned a redirect it will keep
following it even after you change the rule. Test redirects in a private window, and if you need
to clear one, use edge://net-internals/#dns plus a hard reload with
Ctrl+Shift+R. While you are still experimenting, consider using
302 and switching to 301 once it behaves.
Nothing beyond the domain registrations you have already paid for. Cloudflare zones, Universal SSL certificates, Custom Domains on Workers, and Single Redirects are all included on the Free plan. Static asset requests through Workers are free and unlimited. Supabase stays on its free tier. The only recurring cost is the annual renewal of the three names.