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:15 +03:00
1 parent e28d86d7e4
commit 31438b7c90
3 files changed
+98 -2

No files matched your search

+3 -1
View File
@@ -530,7 +530,9 @@ Use \fBauthcache\fR to speedup authentication. RADIUS feature is currently exper
.br
Nameserver to use for name resolutions. If none specified
system routines for name resolution is
used. Optional port number may be specified.
used. 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.
An IPv6 address has to be enclosed in square brackets: