custom domain and mapping failed
-
created new blog. purchased an upgrade package including custom domain and mapping. got the receipt of payment but it seems to have failed. what to do?
The blog I need help with is: (visible only to logged in users)
-
Exactly what failed?
And what is the domain URL?
Did you follow the instructions to set up domain mapping?
If you did then it can take up to 72 hours propagation time.All that changes when you are domain mapping is the URL and nothing else. The content stays exactly where it is. What domain mapping does its create a seamless transfer between the underlying .wordpress.com blog URLs to the domain URLs no matter where they are on the internet. Visitors who click the underlying .wordpress.com blog URLs will be seamlessly redirected to the exact same content under the domain URLs.
Please read Domains: Important Notes Before Upgrading http://en.support.wordpress.com/domains/
In order to map to a domain one must have an underlying .wordpress.com subdomain blog to map from, and the domain name you desire must be available for purchase, or you must already own the domain URL.
You must be logged in as Admin http://en.support.wordpress.com/user-roles/#administrator under the exact same username account that registered the blog to access the blog’s dashboard at > Store > My Upgrades to purchase upgrades for the blog.
See here if you do not own a domain http://en.support.wordpress.com/domains/
See here for mapping an existing domain that you already own http://en.support.wordpress.com/domains/map-existing-domain/
if you already have a website you don’t want to affect, and you want to add a blog to it under a subdomain (for example, blog.yourgroovydomain.com) see here http://support.wordpress.com/domain-mapping/map-subdomain/
After you do the primary blog set up it can take between 24 – 72 hours for domain name propagation to take place throughout the internet. You can view the DNS changes here > http://www.whatsmydns.net/ What’s important during that stage is to be patient.
-
thank you for your reply. i’ll give it the 72 hours. meanwhile, i’ll check out your suggested links.
aa
-
I can save you grief and time if you answer the question I asked above please.
And what is the domain URL?
-
thank you for your time. i went to the store and upgrades and even though it had charged my account was not registered. did it a gain and problem solved. thanks for the tips.
aa
-
What is the URL starting with http:// of the custom domain please?
I am asking for a third time because when I click this link https://foodielady.wordpress.com/ I find zero evidence of any domain mapping.
Are you referring to http://foodielady.com/? If you are then you are posting to the wrong support forum and we cannot help you here with that or with any WordPress.ORG software install.
foodielady.com is hosted by iPage
WHOIS
IP Address: 66.96.160.147
Name Servers:
ns2.netfirms.com
ns1.netfirms.comWordPress.COM and WordPress.ORG are completely separate and have different username accounts, logins, features, run different versions of some themes with the same names, and have separate support documentation and separate support forums. Read the differences here http://en.support.wordpress.com/com-vs-org/
If you need help with a WordPress.ORG software install in the future and don’t have a username account at WordPress.ORG click http://wordpress.org/support/ and register one on the top right hand corner of the page that opens, so you can post to the support forums there.
Resetting your WordPress.ORG password http://codex.wordpress.org/Resetting_Your_Password
WordPress.org support docs are at https://codex.wordpress.org/Main_Page -
as i mentioned in my initial message, it’s for a new blog that at this point is private elcaminomyway.com
i followed your recommendations and the problem IS SOLVED.
foodielady.com is also mine and is working fine.
thank you for your assistance.
aa
-
I am so sorry I missed that but glad I was able to help on this busy Monday Morning. best wishes for happy blogging. :)
- The topic ‘custom domain and mapping failed’ is closed to new replies.