Hi, @JohannBoumans. Our support team can answer questions about Netlify and our services but we cannot provide technical support for other services. I mention this because the domain
aboutgreen.lu isn’t hosted at Netlify currently:
Name server records (type = NS):
aboutgreen.lu. 3599 IN NS dns200.anycast.me.
aboutgreen.lu. 3599 IN NS ns200.anycast.me.
Records for the apex domain (type = A):
Records for www subdomain:
www.aboutgreen.lu. 3599 IN CNAME aboutgreenmain.gatsbyjs.io.
aboutgreenmain.gatsbyjs.io. 29 IN CNAME us-eu.gatsbyjs.map.fastly.net.
us-eu.gatsbyjs.map.fastly.net. 29 IN A 184.108.40.206
I can share information about how to do this at Netlify though. The steps would be:
- Create the required DNS records (as found in the external DNS instructions) for
aboutgreen.lu like you have already done for
- Add the custom domain to the site as a domain alias (which I see has already be done).
- Add redirect rules to the site and trigger a new deploy with those changes to make those redirects active.
Personally, I prefer the syntax of the
_redirects file. In
_redirects format the required domain-level redirects might look like this:
http://aboutgreen.lu/* https://aboutgreen.eu/fr-lu 301!
https://aboutgreen.lu/* https://aboutgreen.eu/fr-lu 301!
http://www.aboutgreen.lu/* https://aboutgreen.eu/fr-lu 301!
https://www.aboutgreen.lu/* https://aboutgreen.eu/fr-lu 301!
These redirects would send any HTTP requests for any URLs at
www.aboutgreen.lu to the
/fr-lu path at the
I also have one final comment. I see you have made an A record for the apex domain and made the apex domain the primary domain for the site. When using the A record for the apex, we recommend not making the apex the primary domain. There is more about why in this blog post, quoting:
There’s one small but unavoidable downside here: manually setting an A record on your apex domain that points to our load balancer doesn’t let us insert any advanced traffic direction. We have no way of routing users who go to
example.com (without the
www. ) to the closest or most performant CDN node. Luckily, any suboptimal performance will only affect site visitors the first time they go to the bare domain; after that, their browser cache will have the redirect to
www.example.com , where they’ll benefit from our globally distributed infrastructure.
If there are other questions about this, please let us know.