Forum Discussion
Solved
dns subdomains
say I bought domain.com from godaddy. but I only ever want to use the subdomain a.domain.com. I want my office365 email to come from @a.domain.com, not @domain.com. I want to browse to http://a.domai...
- Thanks for your reply. I figured it out after. Turns out this was the key question:
"is godaddy's rule about having a CNAME with the same name as an MX record typical of DNS hosters?"
And the answer is yes. DNS RFC says I can't/shouldn't have a cname record for a.domain.com and an mx record for a.domain.com at the same time. I have to use an A record instead of a cname.
I let office365 create all the records for a.domain.com, and it created them correctly. I just really (thought I) wanted that cname for a.domain.com. But it turns out that I don't really need it-- I can create the cname http://www.a.domain.com, and godaddy's dns will also allegedly let me "forward with masking" a.domain.com anywhere I want while keeping a.domain.com displayed in the address bar.
You are talking about two different things now, GoDaddy DNS records and Office 365 domains.
To get mail flow work in Office 365, you need to add the domain to Office 365 and confirm that you own the domain. This is typically done by TXT record with value like ms=MS11111111. If you're using GoDaddy, I would suggest that you'd do this manually instead of letting Office 365 to do it automatically.
So, lets say you wan't to use ONLY abc.domain.com in Office 365.
- You need to add the domain to Office 365. After that, it shows you the TXT record you need to add to GoDaddy. Note! Make sure that you DO NOT have domain.com registered in Office 365.
- Go to GoDaddy and open domain.com DNS management.
- Add a new TXT record with hostname abc with the ms=MSxxxxxxx generated in step 1.
- Go back to Office 365 and complete the validation
Now the domain is validated and you can add the rest of the records, such as MX and SPF to enable the mail flow. You can also add CNAME records as needed.
Thanks for your reply. I figured it out after. Turns out this was the key question:
"is godaddy's rule about having a CNAME with the same name as an MX record typical of DNS hosters?"
And the answer is yes. DNS RFC says I can't/shouldn't have a cname record for a.domain.com and an mx record for a.domain.com at the same time. I have to use an A record instead of a cname.
I let office365 create all the records for a.domain.com, and it created them correctly. I just really (thought I) wanted that cname for a.domain.com. But it turns out that I don't really need it-- I can create the cname http://www.a.domain.com, and godaddy's dns will also allegedly let me "forward with masking" a.domain.com anywhere I want while keeping a.domain.com displayed in the address bar.
"is godaddy's rule about having a CNAME with the same name as an MX record typical of DNS hosters?"
And the answer is yes. DNS RFC says I can't/shouldn't have a cname record for a.domain.com and an mx record for a.domain.com at the same time. I have to use an A record instead of a cname.
I let office365 create all the records for a.domain.com, and it created them correctly. I just really (thought I) wanted that cname for a.domain.com. But it turns out that I don't really need it-- I can create the cname http://www.a.domain.com, and godaddy's dns will also allegedly let me "forward with masking" a.domain.com anywhere I want while keeping a.domain.com displayed in the address bar.