Question
Website (served by DO) not appearing now that Office 365 email accouunt is set up on Godaddy
- Posted July 20, 2019
- DNSEmailArch Linux
Hello
Our domain is served and managed by DO, happily for several years.
I just switched from using Gmail to office 365 for the email associated with our domain. Godaddy is the supplier of the Office365 package.
I folled the instructions (listed below) and the email account works, but the website is now not appearing.
Is there a fundamental conflict or can I make some changes and solve?
Thanks in advnce
Locate the CNAMEs and set the following:
Name Target autodiscover autodiscover.outlook.com sip sipdir.online.lync.com lyncdiscover webdir.online.lync.com email email.secureserver.net msoid clientconfig.microsoftonline-p.net Locate the MX and set the following:
Host Priority Target @ 0 powtoken-com.mail.protection.outlook.com Locate the SRV and set the following:
Port Protocol Name Service Priority Weight Target 443 _tls @ _sip 100 1 sipdir.online.lync.com 5061 _tcp @ _sipfederationtls 100 1 sipfed.online.lync.com Locate the TXT and set the following:
Name TXT Value @ MS=ms39594265 @ v=spf1 include:spf.protection.outlook.com -all
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hello,
It would not matter where your emails are hosted at as long as your A record is pointing to your Digital Ocean droplet’s IP address.
My guess would be that you either made a change to the A record and now the domain name is not pointing to the droplet, or that you changed your nameservers.
You could use this website here to check your current Nameservers:
https://www.whatsmydns.net/
Just enter your domain name and choose NS from the drop down. If you see the Microsoft Nameservers, then this means that your DNS zone is now managed through Microsoft and you need to go there and add an A record for your domain name to point to the droplet’s IP, and a CNAME record for your www version to point to your domain name itself.
If the Nameservers are still set to the Digital Ocean ones, then you need to check your current A record and make sure that it matches your droplet’s IP.
Hope that this helps, let me know if you need any help!
Regards, Bobby