resolve: a name server answering with an error asks the next one (#735)

A reply with no answers and an error code - FORMERR, SERVFAIL, NOTIMP,
REFUSED - ended the resolution as if the name had no address, and the
servers after the one that answered were never asked, so one broken
server made every name it broke fail. Such an answer is passed over for
the next server now; a reply without data, and one that says the name is
not there, still end the search.
This commit is contained in:
Vladimir Dubrovin committed 2026-11-21 13:59:51 +03:00
1 parent 923b9c8abf
commit da9d1ba892
3 files changed
+99 -2

No files matched your search

+4 -1
View File
@@ -629,7 +629,10 @@ Use \fBauthcache\fR to speedup authentication. RADIUS feature is currently exper
.BR nserver
\fI<ipaddr>\fR[:\fIport\fR][/\fItcp\fR]
.br
Nameserver to use for name resolutions; up to 3, asked in order.
Nameserver to use for name resolutions; up to 3, asked in order; a
server that answers with an error (FORMERR, SERVFAIL, REFUSED and the
like) is passed over for the next one, while a name answered with no
data, or as not there, ends the search.
Optional port number may be specified.
If optional /tcp is added to IP address, name resolution is
performed over TCP.