WORKS2011
asked on
Recursive Queries Error
Not sure why this has just begun happening hasn't been an issue in the past. We did just move from in-house exchange server to Office 365. I check the domain in question at http://intodns.com and get the following notice:
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So what did you change after moving to O365? The MX record? Or did you "delegate" the domain DNS to O365? If the second, the above warning is expected, you are effectively using a shared DNS service now.
ASKER
Something worth mentioning is our ISP had issues on the static IP they gave us. Strange, never seen it before there was a layer 3 device holding a blacklisted IP address on the old static IP. The only way our ISP could get Office 385 to send email was put us on a different static IP. Due to this nothing has changed on our server and we manually configured DNS at Network Solutions.
@Vasil Michev (MVP) we did change the MX records to point to Microsoft. We did this manually at Network Solutions.
@John, our servers been online 4-5 years and never had any issues.
@Vasil Michev (MVP) we did change the MX records to point to Microsoft. We did this manually at Network Solutions.
@John, our servers been online 4-5 years and never had any issues.
ASKER
The IP's in question are owned by Network Solution.
ns18.worldnic.com ['207.204.21.109'] [TTL=7200]
ns17.worldnic.com ['207.204.40.109'] [TTL=7200]
Interesting this wasn't an issue on the other static IP.
Is this anything I should be concerned with? My main goal is no more bounced email while sending email from Office 365. Email is working fine now, however, I prefer proactive approach rather than break-fix.
ns18.worldnic.com ['207.204.21.109'] [TTL=7200]
ns17.worldnic.com ['207.204.40.109'] [TTL=7200]
Interesting this wasn't an issue on the other static IP.
Is this anything I should be concerned with? My main goal is no more bounced email while sending email from Office 365. Email is working fine now, however, I prefer proactive approach rather than break-fix.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As stated, the warning you're receiving is expected and safe to ignore when using registrar dns servers.