Tuesday, October 27, 2020

BIND : DNS Issue #5

 Issue:

dnssec: info: validating 83.0.11.10.in-addr.arpa/PTR: bad cache hit (10.in-addr.arpa/DS)
lame-servers: info: broken trust chain resolving '83.0.11.10.in-addr.arpa/PTR/IN': 8.8.8.8#53
dnssec: info: validating 65.0.11.10.in-addr.arpa/PTR: bad cache hit (10.in-addr.arpa/DS)
lame-servers: info: broken trust chain resolving '65.0.11.10.in-addr.arpa/PTR/IN': 8.8.8.8#53
dnssec: info: validating 114.0.11.10.in-addr.arpa/PTR: bad cache hit (10.in-addr.arpa/DS)
lame-servers: info: broken trust chain resolving '114.0.11.10.in-addr.arpa/PTR/IN': 8.8.8.8#53
dnssec: info: validating 129.0.11.10.in-addr.arpa/PTR: bad cache hit (10.in-addr.arpa/DS)
lame-servers: info: broken trust chain resolving '129.0.11.10.in-addr.arpa/PTR/IN': 8.8.8.8#53
dnssec: info: validating 34.0.11.10.in-addr.arpa/PTR: bad cache hit (10.in-addr.arpa/DS)

Solutions:

1. Edit /etc/bind/named.conf.options
2. Add this file under directory "/var/cache/bind";

.......
dnssec-enable no;
dnssec-validation no;

3. Save the file
4. Restart bind

Related Posts:

  • Prometheus and Grafana : Monitor BIND DNS server 1.Pre-requisites- BIND need to have been build with libxml2 support# named -V | grep libxml22.Installed Bind Prometheus Exporter- Download the l… Read More
  • BIND : DNS Issue #5 Issue:dnssec: info: validating 83.0.11.10.in-addr.arpa/PTR: bad cache hit (10.in-addr.arpa/DS) lame-servers: info: broken trust chain resolving … Read More
  • BIND : DNS Issue #1Q:Why do I get errors like "dns_zone_load: zone foo/IN: loading master file bar: ran out of space"?A:This is often caused by TXT records with missing … Read More
  • BIND : DNS IssueIssue 1 : isc_stdio_open '/var/log/named/named_security.log' failed: permission denied Solutions  :chown -R bind:root /var/log/namedchmod -R 77… Read More
  • BIND : DNS Issue #41. Issue - resolving a local domain name to an IP address fails with:> 192.168.1.3Server:         127.0.0.1… Read More

0 comments:

Post a Comment