Has anyone at EE created a pubic DNS / name server? Here's my scenario:
I've recently migrated to Exchange 2013 servers and during the process, I've updated my (A) and (MX) records to point to a new IP addresses. Mail-flow is working, and all exchange services are working properly. A week later we started experiencing message failures because mail servers on the other end were unable to verify our organization. This of course is a PTR record issue, and in most cases we would usually contact the ISP to generate a PTR record. The only problem is the "new" IP address I need to use, we own. Plan B was to generate a PTR from 1and1.com who handles our domain. Of course, 1and1 does not give us the option to generate a PTR record. I believe what is causing this issue is that I need to upgrade the account to a premium package, but I can't stand 1and1 because I've had nothing but problems with their services. We've subscribed to DYN and we were able to create a record that will validate our messages. During this project, we were required to perform a security audit on our network infrastructure. They of course found issues and want us to address them. One of the issues is the PTR record we created is point to one of our private / internal DNS servers. I agree with their assessment, and I'm in the process of finding the best practice to create a public DNS server that will not have access to any internal resource (Pretty much sitting on the outside of the firewall, on it's own separate public address). Is it best to use a Linux server, or Windows? What things do I need to take into consideration? Any input would be greatly appreciated. Thank you for your time.