01-21-2021 02:30 AM
It is correct was PI is showing in GUI, what is not correct is that the “show running-config” is displaying nameserver which are not configured….
Underlying linux name server configuration in my case:
ade # cat /etc/resolv.conf
# Generated by dnssec-trigger 0.11
domain notimportant.net
search notimportant.net
nameserver 127.0.0.1
ade #
I think manually adding the nameserver to resolv.conf and restarting PI is going to fix the issue, I haven't done that until now, just informed my service provder.
01-21-2021 07:22 AM
Hello community,
it's not a bug it's a featrure:
DNS Enhancements:
Prime Infrastructure 3.9 has brought security to DNS traffic by implementing DNS Security Extensions (DNSSEC). This is enabled by default and can be controlled through new Admin CLI option - 'ip dnssec'.
Disabling dnssec was the solution in my case:
hostname/admin# conf t
Enter configuration commands, one per line. End with CNTL/Z.
hostname/admin(config)# no ip dnssec
hostname/admin(config)# exit
hostname/admin# write memory
Generating configuration...
hostname/admin#
BR
Bastian
05-30-2022 04:41 AM
Hi, had the same issue, just after migration of our dns servers to w2k19.
"no ip dnssec" on prime solved the issue.
thx to all.
br, Thomas
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide