BIND 10 #833: [b10-resolver] Nameservers unreachable but really are
BIND 10 Development
do-not-reply at isc.org
Mon Apr 4 20:09:56 UTC 2011
#833: [b10-resolver] Nameservers unreachable but really are
--------------------------------+---------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: critical | Milestone:
Component: resolver | Keywords:
Sensitive: 0 | Estimated Number of Hours: 0
Add Hours to Ticket: 0 | Billable?: 1
Total Hours: 0 | Internal?: 0
--------------------------------+---------------------------------
I noticed some SERVFAILs in my b10-resolver logging. Apparently,
b10-resolver/nsas is giving up too soon.
Two examples are:
98.156.17.218.in-addr.arpa. PTR
0.1.c.5.1.8.e.f.f.f.1.d.9.1.2.0.a.b.7.1.5.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa.
PTR
which both result in:
[b10-resolver] Nameservers unreachable
and SERVFAIL
I set this to critical since it may not give proper result.
--
Ticket URL: <http://bind10.isc.org/ticket/833>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list