Cisco Prime Version 3.9 DNS Bug

All Prime Infrastructure installations of 3.9 have same issue; regardless of whether it is a fresh install, or a system upgraded from an earlier version. On the Administration > System Monitoring Dashboard > System Information panel, the DNS server's IP address always shows 127.0.0.1, even after being updated from the CLI.

Prime/admin# show running-config | include name-server

ip name-server x.x.x.x x.x.x.x

Prime/admin#

Prime/admin# show running-config | include dnssec

ip dnssec

Prime/admin#

 ade # cat /etc/resolv.conf

# Generated by dnssec-trigger 0.11

domain xyz.org

search xyz.org

nameserver 127.0.0.1

ade #

 

This was observed in Prime Infrastructure 3.9 when DNS Sec is enabled, which is the default setting. See the Release Notes for Prime Infrastructure 3.9 at https://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-9/release/notes/bk_Cisco_Prime_Infrastructure_3_9_0_Release_Notes.html

Workaround:
If DNS Sec is enabled, there is no workaround. If DNS Sec is intentionally disabled in the network, the DNS server configuration can be refreshed by disabling DNS Sec at global config, then redefining the DNS servers. The commands to do that are:

config t
no ip dnssec
ip name-server x.x.x.x
write mem

Comments

Popular posts from this blog

FortiGate Firewall Unused Policy Clean up

Cisco Prime Inline Upgrade Procedure

How to create DNS entry for newly built Server.