Please explain how to map only a sub-domain (an A record) of an existing domain
-
Please explain how to map only a sub-domain (an A record) of an existing domain to a WordPress hosted blog.
There is no logical reason to not support A record mappings.
Asking for customers to use WordPress.com name servers for their entire domain introduces technical constraints, and potential operational risks, that are unacceptable and will prevent many from using the service.
The blog I need help with is: (visible only to logged in users)
-
http://en.support.wordpress.com/domains/map-subdomain/
It’s right there in the Support documents. I dunno where you’re getting all these erroneous preconceptions, but they are erroneous.
-
Thanks for providing the link to the map-subdomains support document.
That link wasn’t provided by the automated support tool and I didn’t see any cross-reference to the map-subdomains topic from the map-existing-domain topic. It appears that there is a cross-link, however it is buried in a paragraph mid-way through. Probably should be highlighted towards the top.
http://en.support.wordpress.com/domains/map-existing-domain/
-
Specifically, the following is buried toward the end of Step 2, around the mid-point of the page.
This information should appear toward the top of the document.
Alternatively, you can map a subdomain to your WordPress.com site, which doesn’t require changing the name servers and will not affect any custom DNS records at your registr
-
- The topic ‘Please explain how to map only a sub-domain (an A record) of an existing domain’ is closed to new replies.