cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1679
Views
0
Helpful
7
Replies
Highlighted
Frequent Contributor

CUCM 10.5.2. - Reverse DNS lookup mismatch

Hi Guys,

 

I am trying to put the IM&Presence in production, but, as the service Cisco Sync Agent is status (Stopped) and not running, I am suspecting that have any relation wih DNS that is presenting the error message: Reverse DNS lookup mismatch. This message is appearing in the All Servers (CUCM, CUC and Presence). Any have idea as solve the problem about DNS?

 

 

Thanks,

 

Regards,

 

Wilson

Everyone's tags (1)
7 REPLIES 7
Highlighted
Hall of Fame Master

Re: CUCM 10.5.2. - Reverse DNS lookup mismatch

Do you have all servers properly defined in corporate DNS?

What does "nslookup" from your machine return for both forward and reverse inquiry?  Try it multiple times for each entry as there may be a record pointing to different destinations and DNS would just round robin it.

Highlighted
Frequent Contributor

Re: CUCM 10.5.2. - Reverse DNS lookup mismatch

Hi Chris,

 

Thanks a lot for Your contact. I applied the command nslookup for all servers and had this output:

 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\User>nslookup
Default Server:  SERVER003.XYZW.local
Address:  10.96.101.3   >> This is a DNS Primary Server

 

> server 10.96.104.1
Default Server:  SERVER-CUCM-Pub1
Address:  10.96.104.1

> SERVER-CUCM-Pub1
Server:  SERVER-CUCM-Pub1
Address:  10.96.104.1

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to SERVER-CUCM-Pub1 timed-out
>
>
> server 10.96.104.2
DNS request timed out.
    timeout was 2 seconds.
Default Server:  [10.96.104.2]
Address:  10.96.104.2

> SERVER-CUCM-Sub1
Server:  [10.96.104.2]
Address:  10.96.104.2

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to [10.96.104.2] timed-out
>
>
> server 10.96.104.3
DNS request timed out.
    timeout was 2 seconds.
Default Server:  [10.96.104.3]
Address:  10.96.104.3
>
>
> SERVER-CUC-Pub1
Server:  [10.96.104.3]
Address:  10.96.104.3

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to [10.96.104.3] timed-out
>
>
> server 10.96.104.4
DNS request timed out.
    timeout was 2 seconds.
Default Server:  [10.96.104.4]
Address:  10.96.104.4
>
>
> SERVER-CUC-Sub1
Server:  [10.96.104.4]
Address:  10.96.104.4

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to [10.96.104.4] timed-out
>
>
> server 10.96.104.5
DNS request timed out.
    timeout was 2 seconds.
Default Server:  [10.96.104.5]
Address:  10.96.104.5
>
>
> SERVER-CUP-Pub1
Server:  [10.96.104.5]
Address:  10.96.104.5

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to [10.96.104.5] timed-out
>
>
> server 10.96.104.6
Server:  [10.96.104.6]
Address:  10.96.104.6

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to 10.96.104.6 timed-out
>
>
> SERVER-CUP-Sub1
Server:  [10.96.104.6
Address:  10.96.104.6

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to [10.96.104.6 timed-out
>

 

Thanks,

 

Regards,

 

Wilson

Highlighted
Hall of Fame Master

Re: CUCM 10.5.2. - Reverse DNS lookup mismatch

Looks like you have some issues there as you are getting the DNS timeout errors, double check you DNS servers to make sure both forward and reverse lookups are correctly defined.

Highlighted
Frequent Contributor

Re: CUCM 10.5.2. - Reverse DNS lookup mismatch

Hi Chris,

 

I requested to my Co-worker verify again the DNS Server then I answer for You about the results.


Thanks,

 

Regards,

 

Wilson

Highlighted
Beginner

Re: CUCM 10.5.2. - Reverse DNS lookup mismatch

just make sure your IMP and CUCM have same version. if not please upgrade your IMP version same with CUCM version

 

for DNS, please do test connection first.

and then make sure A & PTR record already create on your DNS server

 

 

Regards,

 

 

Regards, Habibi
Highlighted
Frequent Contributor

Re: CUCM 10.5.2. - Reverse DNS lookup mismatch

Hi Habibi,

 

Thanks a lot for Your contact.

 

I have the following version o CUCM and IM&Presence

 

Cisco Unified CM Administration
System version: 10.5.2.15900-8
VMware Installation: 1 vCPU Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz, disk 1: 80Gbytes, 4096Mbytes RAM, Partitions aligned
WARNING: DNS unreachable


Cisco Unified CM IM and Presence Administration
System version: 10.5.2.24900-8
VMware Installation: 1 vCPU Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz, disk 1: 80Gbytes, 4096Mbytes RAM
WARNING: DNS unreachable

 

About DNS, only my co-worker have access the DNS Server (He is verifying) and I too not know about DNS.

 

Thanks,

 

Regards,

 

Wilson

Highlighted
Beginner

Re: CUCM 10.5.2. - Reverse DNS lookup mismatch

Hi

First you will want to verify that your UC applications are configured with the correct DNS Primary and Secondary issue command on CLI of application show network eth0 and note the result.

 

2. If it checks out then you can issue: utils diagnose test and see if the DNS is resolved.

 

3. If it is not verify that the forward and reverse lookup zones are configured. I found that if the forward was created and the reverse was not created at the same time just adding the reverse does not work. You will have to delete the forward and recreate it but this time choose to create the reverse PTR one time.

4. Run: utils diagnose test and see if the DNS is resolved

CreatePlease to create content
Content for Community-Ad
Future of Work Virtual Summit Day 5

Cisco COVID-19 Survey