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:
hsr
LVL 17
WORKS2011Managed IT, Cyber Security, BackupAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jon BrelieSystem ArchitectCommented:
You should not allow recursive queries on public servers.  It basically means that your DNS server will query other DNS servers in order to resolve any domain queried and pass the info back to the requesting client.

You want your DNS servers to say, "I don't know" and leave it at that when queried to resolve domains that it is not authoritative for.  (ie: make sure you aren't using the same dns server for internal and external.)
Vasil Michev (MVP)Commented:
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.
WORKS2011Managed IT, Cyber Security, BackupAuthor Commented:
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.
Are You Protected from Q3's Internet Threats?

Every quarter, WatchGuard's Threat Lab releases a security report that analyzes the top threat trends impacting companies around the world. For Q3, we saw that 6.8% of the top 100K websites use insecure SSL protocols. Read the full report to start protecting your business today!

WORKS2011Managed IT, Cyber Security, BackupAuthor Commented:
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.
Jon BrelieSystem ArchitectCommented:
No, if you are using registrar DNS servers, then the message you received is completely expected and safe to ignore.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jon BrelieSystem ArchitectCommented:
As stated, the warning you're receiving is expected and safe to ignore when using registrar dns servers.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Office

From novice to tech pro — start learning today.