our docs have a lot of the information you will need to get started:
if you use the search for this site, you will also see that we have answered a lot of subdomain related questions, it is very likely that any questions you might have are already answered
You can use the search on this community forum for anything you would like. If you are setting up a subdomain for your site, you can use the search as follows after reading the docs to see solutions for previous posts.
I’ve read through the documentation and worked it out.
There was some information that came up in my dashboard about a CNAME entry on my DNS provider. I didn’t manage to note the information and it won’t display again.
Hi, @berni, do you want to change the subdomain used at Netlify for the site? If so, this is done by going to “Site Name” > Settings > General > Site details and then click the “Change site name” button.
Now, if you want to point custom domains to a Netlify site, they are first added to the site under “Site Name” > Settings > Domain management > Custom domains.
The DNS configuration for the custom domain must also be correct. Please use these instructions below if you do not use Netlify DNS:
Or these instructions if you do use Netlify DNS:
If there are questions about any of this, please let us know.
Hi, @berni, the first rule should work in most cases.
It if isn’t working, it would be helpful to examine the actual site at Netlify to find out why. What is the URL which should be working and isn’t? I ask because the domain www.vendors.my-domain.com isn’t hosted at our service and I need to know the actual URL to answer.
Could you link us to a deploy in your deploy history where you had it in place as a 200? redirects are deploy-specific, so we can perhaps find it if you link us to the logs page for that build, to look at what you had written.
The rule doesn’t have a “force” option so it will not proxy for content which does exist. If you want the 200 rule to always proxy, even for content which exists at the current site, then force the proxy like so:
[[redirects]]
from = "https://www.vendors.wherecanibuyit.online/*"
to = "https://www.wherecanibuyitonline.me/:splat"
status = 200
force = true
[[redirects]]
from = "https://vendors.wherecanibuyit.online/*"
to = "https://www.wherecanibuyitonline.me/:splat"
status = 200
force = true
Note, I also added a “splat” rule to keep the path when proxying. Would you please test the two rules above and let us know if they work as required?
browser fetches and displays https://www.wherecanibuyitonline.me (content starts with <!doctype html><html lang="en"><head><meta name="title" content="Where Can I Buy It Online - Vendor Dashboard"/>)
Perhaps your blank page was related to something else - I see what you demonstrated, except, at the original URL as shown in this screenshot:
It has resolved the issue. However the second rewrite speed is much slower than the first. Is it possible to make the speed of the second rewrite the same speed as the first?
Our caching is opportunistic; we don’t pre-cache things like that rewrite, we cache it as it is first requested. I suspect that you’ll see faster performance on subsequent loads from the same CDN node.
I see 3 slow loads, and 32 fast loads over the past 7 days on that URL.