mapping of a single naked domain to multiple subdomain on one wordress.com blog
-
Hi Support,
We have an existing customer who is persistent on using wordpress.com instead of a self hosted wordpress. However, due to a challenging domain structure that they have and a very challenging customer, we are compelled to ask this question despite the very clear documentation on your website about domains http://en.support.wordpress.com/domains/ which they also have read.
The challenge we are facing is that they want their naked domain to point to a subdomain but on the same domain name.
Here is the example:
website.com to blog.website.com (which is feasible using the mapping to subdomain) they also want the flexibility to be able to point website.com to anotherblog.website.com (feasible with another purchase of the mapping of subdomain) but they only want to purchase the mapping of the domain.
Therefore, our question is, would wordpress.com allow wildcard domain for the purchase of the domain mapping or would there be an ability on the wordpress.com domain administration to be able to map the naked domain to any subdomain at the discretion of our customer?
The blog I need help with is: (visible only to logged in users)
-
In your example, would blog.website.com be hosted here and would anotherblog.website.com also be hosted here?
I’m not staff (although I have flagged this for their attention) but in my experience I’ve seen this done at least once in the past eight years. I’m pretty sure this is doable, but stay on the line for the staff response.
-
hi raincoaster, thanks for your reply. Our customer would want it hosted on wordpress.com. however, we have not yet cleared with our customer whether the structure they want is actually:
[1]
website.com –> blog.website.com –> webblog.wordpress.com
website.com –> anotherblog.website.com –> webblog.wordpress.comor
[2]
website.com –> blog.website.com –> webblog.wordpress.com
website.com –> anotherblog.website.com –> anotherwebblog.wordpress.combut it was communicated previously that [1] is their option, however, [2] may actually be what they are thinking of.
Many thanks!
-
As far as I know, 2 is doable but I doubt very much 1 is. Why would you even want it? But staff will have the final say.
-
So far, its not that I want or need [1] but its more of a requirement we have to satisfy. Like what I have said, this is for a very challenging customer. Normally, our team will not bother to ask support because of the wealth of documentation on wordpress.com and the experience of people on the support forums. I am actually convinced that [2] is what our customer want but we still have to confirm.
Thanks!
-
Thanks raincoaster for the responses. I think the staff may not be able to help out on this and will not have the final say but I believe that issue can already be resolved!
-
Hi there,
Sorry to ask for additional clarification, but as you said this domain structure is a bit complicated!
To clarify, is your client looking to have a setup wherein if a visitor goes to (for illustrative purposes): example.com, they are redirected automatically to welcome.example.com (which stays in the location bar), and which pulls up the source material which is hosted on example.wordpress.com?
Let me know!
-
It should be noted that at no point would any of this be easily editable by your client. Updating mapping is something which has to be completed by support on our end, so if they want to change something along those lines we would need to change it for them.
With that said, if they only would need to change their DNS, we have a fully functional DNS management system which they could modify at any time.
-
Hi amightywp, thanks for the reply.
We have already clarified with our customer and already purchased an upgrade. Though, as we have explained to them that we are unsure if the one we purchased for them will give them the ability to perform the second example. A bit of clarification because I think what we have illustrated maybe confusing.
As our understanding and based on the forums/documentation that http://www.domain.com –> [redirects to ] –> domain.com.
reillustrated for clarification on our second example
blog.wordpress.com –> website.com
anotherblog.wordpress.com –> subdomain.website.comHas our purchase of the upgrade will allow them to add the anotherblog –> subdomain? Or do we need to do something or ask the staff to add the entry on wordpress.com dns?
Though they are quit satisfied with blog –> naked, they are still considering anotherblog –> subdomain.
Kindly, look at our existing settings, if you may.
Thanks!
-
anotherblog.wordpress.com –> subdomain.website.com
This is not functionality that is available on WordPress.com I am afraid.
-
Hi rootjosh, appreciate the response.
Then what should our customer upgrade should they want to be able to achieve this functionality or do we need to ask the staff’s assistance to be able to accomplish and utilize the fully functional DNS management system to satisfy the requirement of our customer?
To the Happiness Engineers, Staffs, and members who responded, Thank you for the help and assistance!
-
I do not think you will be able to satisfy your client’s requirements on WordPress.com.
You might consider looking into setting up a self-hosted WordPress.org site. There is additional flexibility that should help you.
-
To be honest, we are very much aware of the difference between wordpress.com and self-hosted solution. However, we do not know which functionality that are available with the dotcom that is why we are asking. And because we have a number of request if they could use dotcom instead of the other and help them establish their wordpress.com presence. Our core competence is not web development but publication though we keep on receiving request from clients such as this.
I understand the sentiments and appreciate an honest response.
-
WordPress.com is a great platform. But for highly customized site, or one with very specific requirements, self-hosted WordPress.org is probably the way to go.
- The topic ‘mapping of a single naked domain to multiple subdomain on one wordress.com blog’ is closed to new replies.
WordPress.com Forums 