I have a primary DNS with Windows 2008 R2 Standard named DNS01.MYDOMAIN.COM and adding now 2 new DNS servers with Windows 2016.
None of these 3 server have active directory because they will be used exclusively for resolving public names pointing to our servers (such as our mail, some webservices, some webpages, etc.).
These 2 new DNS servers with Windows 2016 with the DNS roles will be used as the "backup" or "failover" servers (these new 2 servers will be physically in another location) and they are (for now) named NEW-DNS02.MYDOMAIN.COM and NEW-DNS03.MYDOMAIN.COM.
NOTE: None of these 3 servers belong to any Domain Controller. They are all standalone servers with the sole purpose of resolving names on my network.
When I am adding in the Name Servers tab of the primary DNS (DNS01.MYDOMAIN.COM), I am typing the name NEW-DNS02.MYDOMAIN.COM as the FQDN and click RESOLVE. While resolving it does bring the correct public IP and shows VALIDATING. But after a minute it brings “A timeout occurred during validation.”. Even with this error, it seems it added the record.
- Should I ignore this error at the end?
While trying to figure out the error, I typed the internal IP of the NEW-DNS02.MYDOMAIN.COM just below the space where I type the FQDN, the validation shows OK and turns green, but the OK button is not enabled.
So with these last discovery, I created a new A record with the name TEST-DNS02.MYDOMAIN.COM with the Internal IP and tried again using TEST-DNS02.MYDOMAIN.COM as the FQDN (but remember this A record has the internal IP of the server). This time the validation went OK and it added the record as a Name Server.
- Is there any problem if the FQDN points to an Internal IP?
- Is there any other reason that when the FQDN points to an external IP the validation fails?
- What I did above is considered to be good and leave it like that?