critical: resolver.c:5125: INSIST(dns_name_issubdomain(&fctx->name, &fctx->domain)) failed
Summary
critical: resolver.c:5125: INSIST(dns_name_issubdomain(&fctx->name, &fctx->domain)) failed
This problem does not always appear, sometimes it is good and sometimes bad
BIND version used
9.16.6
Steps to reproduce
info: client @0x7f36b4445450 [redacted]#20761 (172.231.232.183.in-addr.arpa): view [redacted]: query: 172.231.232.183.in-addr.arpa IN PTR + ([redacted])
query-errors: info: client @0x7f45d40de490 [redacted]#3072 (closed) (246.146.194.221.in-addr.arpa): view [redacted]: query failed (SERVFAIL) for 246.146.194.221.in-addr.arpa/IN/PTR at query.c:6217
What is the current bug behavior?
Abnormal reverse dns lookup
What is the expected correct behavior?
This issue will not be triggered in version bind9.16.5
Relevant configuration files
[redacted]
Relevant logs and/or screenshots
queries.log:
info: client @0x7f36b4445450 [redcated]#20761 (172.231.232.183.in-addr.arpa): view [redacted]: query: 172.231.232.183.in-addr.arpa IN PTR + ([redacted])
default.log:
lame-servers: info: REFUSED unexpected RCODE resolving 'tracker.iamhansen.xyz/AAAA/IN': 108.162.192.130#53
query-errors: info: client @0x7f45d40de490 [redacted]#3072 (closed) (246.146.194.221.in-addr.arpa): view [redacted]: query failed (SERVFAIL) for 246.146.194.221.in-addr.arpa/IN/PTR at query.c:6217
general.log:
critical: resolver.c:5125: INSIST(dns_name_issubdomain(&fctx->name, &fctx->domain)) failed