Sign up for Office 365
Learn more about Office 365
I have several sites that i have moved from OfficeLive. 2 of gthem moved OK and others did not. the difference between the ones that workl and the ones that don't appears to be in the way Microsoft 365 sees the DNS records.
typically, the working domains have 2 more dns records than the ones that don't....
the CNAME www record and
the A @ record
When I look at my own dns management for any of these domains, working or not, I do not see the records that I see in the 365 page (e.g. below), I just see my defaults for my domain registrar/host. All domains have the nameservers pointing correctly and have had this for a week. As far as I am aware, I used the same steps for all domains when creating my new 365 sites. So how did some not get the extra 2 records??
(I've replaced the real domain name with xxx in the exmple below)
Thanks again for your clarification and sorry to give your response in a late time.
I tried to re-describe your questions in my own word and see whether we are in the same way.
> You have subscribed five Office 365 tenants, i.e. capitalofcaring.onmicrosoft.com, godschildrenuk.onmicrosoft.com, mentalhealthconnections.onmicrosoft.com, werenthousesliverpool.onmicrosoft.com and webuyhousesliverpool.onmicrosoft.com. In the meantime, you have bought five domains from 123-org.co.uk.
> You have added two domains capitalofcaring.com and godschildren.co.uk in two Office 365 tenants and changed public website URL to your own domain. They are working now. You can open them thru IE and use dedicate user accounts to login.
> But if you do the same work for rest three domains, they are not working and missed A Record and CNAME record when using NSLook up tool to check DNS records. But actually they should have.
Let me know if I got any misunderstanding.
I checked your SharePoint sites which should be created with default addresses, they are working and addresses for your public websites which cannot be used for your own domain are:
- mentalhealthconnections.co.uk ---> mentalhealthconnections.sharepoint.com
- werenthousesliverpool.co.uk ---> werenthousesliverpool.sharepoint.com
- webuyhousesliverpool.co.uk ---> webuyhousesliverpool.sharepoint.com
That means public websites was created successfully and A record should be ready for these sites.
Now I think you need to check whether you have changed these default public websites address to your own domain. The workaround should be the same as what you have done for capitalofcaring.com and godshildren.co.uk.
I have checked the CNAME for these domains, you are right they were not created correctly. I can only find CNAME for xxx.sharepoint.com, not your domain.
Hence could your park your public website domain back to xxx.sharepoint.com, then re-change to your own domain. Please follow below steps to do it:
> Log in to the Office 365.
> Go to Admin page
> Click Domains under Management section from left Navigation and go to Domains page.
> On this page you will find a text shows like "Your SharePoint website address is www.xxx.com. | Change Address". Click Change Address and in the pop up window change the domain to your own domain. It needs time to make it work.
If it cannot solve your issue, could you park your name servers to these domains back to your domain registrar and re-point them to Office 365 again, then change address to your own domain for your public websites.
Microsoft Office 365 Support
1 out of 1 people found this post helpful.
Hi edardg,Sorry to give your feedback in a late time. According to your description I think you are the Small Business and Professional tenant of Office 365. What you have done is that you have added your own domain in Office 365. After that did you change your name servers from your domain registrar to Office 365. That means you need to change your name servers from your domain registrar to Office 365. How to change your name servers from your domain registrar to Office 365 you can follow below steps: > If your domain registrar comes from Go Daddy, Melbourne IT, Network Solutions, Hover, eNom Central and Register.com you can refer to http://onlinehelp.microsoft.com/en-us/office365-smallbusinesses/gg549203.aspx. > If your domain registrar is not listed above, you can find the domain where you can change your name servers. And then change the name servers to ns1.bdm.microsoftonline.com and ns2.bdm.microsoftonline.com. Your name server record updates may take up to 72 hours to propagate through the DNS system. Your custom domain will be ready to use with Office 365 after DNS propagation finishes.Then you can use some DNS Lookup tool to check whether these DNS records are workable. And then you can change your public website using your own domain.
Best RegardsMartin XuMicrosoft Office 365 Support
Hi edardg,Did my answer help you? Let us know if you need further assistance from us.
Hi... i tried repoy a few days agfo but I have hgad a lot of trouble accessing this question again.
I can tell you that your advicxe is not the answer,
The problem persists on 3 of the 7 or 8 domains that I used to have with the expired office application.
For all bar those 3, I can access the websites via my domain URL's. For example, the domain called 'capitalofcaring.com' can be accessed in a web browser by typing in www.capitalofcaring.com. These domains have DNS setting to the default for the domain hosting company (123-reg.co.uk) and no web forwarding, these domains show the full 6 records in the tabvle 'Microsoft DNS records for Microsoft Office 365', as listed in my earlier message.
Fpor the 3 domains still not working, I note that there are only 4, not 6 such records. the missinng ones being www and @ as described before.
I have waited MAY days for the name servers to take effect. For the domains that are working, this took much less than 3 days. One was within a minute. For the ones that don't work, they have been set for many, many days and still it does not work. I have even gone back to square ine and rest everything again. I have waited and waited. NO SUCCESS.
The 3 domains with problems are:
( the last 2 domains I manage for a colleague)
All 3 domain names are with 123-reg.co.uk
To get the associated websites visible to the world, I temporarily tried setting web forwarding to point at the sharepoint URL you gave us.For example, mentalhealthconnections.sharepoint.com/.../default.aspx. But I have now felt it necessary to reset to 'no web fowarding' while I ask for your help again, which of course meansthat the sites are not visible at all. DNS recors are set to default for 123-reg.co.uk, THE SAME as for the domains that have working websites/url's
PLEASE PLEASE can you fix this?
...sorry for typos. I have been using my mobile.
Hi edardg, Thanks for your clarification for this question. Now I'm clear what you have done and what you want to implement. In Office 365 you are only allowed to have 1 vanity domain linked to your public-facing website. Office 365 does not provide the ability to have more than one domain directed to your public-facing site. That means if you added one custom domain in Office 365 and set this domain to be a public address to your public website, other domains cannot be set as a public website address in Office 365. That's why your other three domains cannot find the A record and CNAME record even you have added them in Office 365 and chaged Name servers to Office 365. The way you can do is what you did till now. It means don't move name servers of these three domains to Office 365 and let them be hosted by domain registrar. And redirect domain to the only one domain which you are using to your public website. For example you have xxx.com, and this domain to be set as a direction to your public website. And you have another domain yyy.com. Now you want this domain can also open your public website. The approach you can do is redirect yyy.com to xxx.com. Some threads in our community that you can refer are: > http://community.office365.com/en-us/f/152/p/47846/170764.aspx#170764. > http://community.office365.com/en-us/f/148/p/18021/86116.aspx#86116. > http://community.office365.com/en-us/f/152/p/18497/88685.aspx#88685.
Hi Martin... thank you so much for your really quick reply!
Unfortunately, it is still not the answer. I should have made it clearer that, for each of the domains that I want to associate a unique webiste, I created ITS OWN UNIQUE ACCOUNT in Office 365. I was aware of this restriction from the start. And so each of the 3 domains I have trouble with also has there own account. The user logins/ids for these accounts are as follows...
for my domain and website for - mentalhealthconnections.co.uk - my user id is - email@example.com
for my domain and website for - werenthousesliverpool.co.uk - my user id is - firstname.lastname@example.org
for my domain and website for - webuyhousesliverpool.co.uk - my user id is - email@example.com
ALL of the above have their own websites but NONE of those websites can be accessed by their domain names
To help you to understand what i am saying, and that the problem is not as you describe, here are the same details for 2 other domains that ARE WORKING OK in Office 365, where the websites that I also built in Office 365 CAN be accessed by their domain names in the correct way.
for my domain and website for - capitalofcaring.com - my user id is - firstname.lastname@example.org
for my domain and website for - godschildren.co.uk - my user id is - email@example.com
To clarify even further, the first of these two websites, (capitalofcaring.com) is shared by other domains that I own, for example twiggyandbeaky.com. But I was always aware of the rule that you described and so those other domains DO NOT have an account on office 365... I simply use redirect (web forwarding) for them. I think that is what you were suggesting I do to fiox the problem. But as you can see, it is not the same problem.
Maybe you could try popping those names in your brwoser to see what i mean?
I hope that this now makes more sense. It is not easy to describe.
have a happy day,
this did it! Thank you. With so many things to configure, I can see how it was not so easy for me to spot it, but it shows that I wasn't quite as organised amd methodical as I thought! thanks.