On 10/20/20 7:29 AM, cagsm wrote:
I can not nslookup anything using this bind on 127.0.0.1 I suppose this has something got to do with DNSSEC or such stuff? how come a simple security update or patch suddenly activates such a harsh feature midstream in 15.2? or are some root anchors or whatever such stuff missing from the opensuse leap 15.2 update/patch package missing or something?
I can nslookup fine using the ip address of my local broadband router of the ISP i use or with the help of outside resolvers/forwarders e.g. dns.google. or such services in the public.
any quick remedy? thanks lots.
Well, you need to generate your tsig keys so dhcp can provide dynamic updates to your bind zone files. I have some notes on it somewhere. It hasn't changed in ages -- so there may be something else going on. Now if there was a new named.conf file that changes the criteria and requirements for RRSET (record resets, etc...) then that may be another area. Late here and I have a meeting in the morning, I'll check after that. In the mean time show the output from journalctl -u named and if used journalctl -u dhcp4 (and 6 if you use it) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org