summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
4423286)
@@ -23,6 +23,8 @@
+ * Referrals with RD+RA set, or RCODE=Refused, don't generate warnings,
+ just debug messages. BIND does this kind of thing all the time.
* m1test script can invoke `hrecord' differently.
* regress/output-<case>.report file contains more useful info.
* TODO list and other docs updated slightly.
* m1test script can invoke `hrecord' differently.
* regress/output-<case>.report file contains more useful info.
* TODO list and other docs updated slightly.
+ * Referrals with RD+RA set, or RCODE=Refused, don't generate warnings,
+ just debug messages. BIND does this kind of thing all the time.
if (qu) adns__query_fail(qu,adns_s_rcodenotimplemented);
return;
case rcode_refused:
if (qu) adns__query_fail(qu,adns_s_rcodenotimplemented);
return;
case rcode_refused:
- adns__warn(ads,serv,qu,"server refused our query");
+ adns__debug(ads,serv,qu,"server refused our query");
if (qu) adns__query_fail(qu,adns_s_rcoderefused);
return;
default:
if (qu) adns__query_fail(qu,adns_s_rcoderefused);
return;
default:
if (!flg_rd)
adns__diag(ads,serv,qu,"server thinks we didn't ask for recursive lookup");
else
if (!flg_rd)
adns__diag(ads,serv,qu,"server thinks we didn't ask for recursive lookup");
else
- adns__diag(ads,serv,qu,"server claims to do recursion, but gave us a referral");
+ adns__debug(ads,serv,qu,"server claims to do recursion, but gave us a referral");
adns__query_fail(qu,adns_s_invalidresponse);
}
return;
adns__query_fail(qu,adns_s_invalidresponse);
}
return;