Recently upgraded a UC environement from 10.5 to 11.5. After the upgrade was complete, the CUCM Publisher server displayed a “DNS Unreachable” error upon logging into the Administration webpage.
This warning message only appeared on the CUCM Publisher and not the subscriber etc. I confirmed DNS had been configured identically for both the publisher and subscriber. I read that CUCM Version 11.x no does a couple of more network tests that have a direct impact on warning/error messages being displayed on the GUI. One of these tests is against the DNS Reverse Lookup Zone. Pre 11.x versions.. The CUCM server would check to see if a PTR record existed for the hostname, in fact this is required for CUCM installation process to succeed. In version 11.x the CUCM now also continuously checks against the Reverse Lookup Zone for mismatches and displays a warning message on the GUI. In my case, the customer had created an additional A Record for user friendly purposes called myphone.domain.com.au, this automatically created a PTR record. So when CUCM ran checks against the Reverse Lookup Zone, the results displayed a mismatch. Hence the warning was raised and displayed. (Although DNS was functioning perfectly)
Removing this PTR Record resolved the issue with the warning message.
I ran the command “utils diagnose test” to pin point the issue.
so was this essentially just cosmetic then, since DNS continued to work even before you removed the second record, or was there a functional impact?
Dealing with this issue now, for the same reasons.
Yes, could say cosmetic. The system continues to function as per normal, however as with the other mandatory requirements ie Disk Alignment for VM etc TAC may not support the system until the DNS warning has been resolved.
Hi Ben,
Since I am also facing this issue have you resolved.
Can you share how this problem got resolved
You will need to access the Reverse Lookup zone on your DNS server for CUCM subnet. Look for any PTR records that have the CUCM FQDN. There should only be one. However, if there is two PTR records with the same FQDN Name, CUCM will throw a DNS warning message. Just remove the PTR record that has the incorrect IP Address associated to it.
Ben
I am trying the same problem, but, still not was possible found the solution.
Could be a few other reasons, but all to do with DNS configuration. Confirm A records are fqdn, confirm PTR records are fqdn, confirm DNS server have replicated records, confirm correct DNS servers are being queried. Ensure one a single type of record exists for each UC server.