Opened 7 years ago

Closed 7 years ago

#1501 closed defect (wontfix)

multiple resolver would not down if keep failing

Reported by: crasyangel.lhy@… Owned by:
Priority: critical Milestone:
Component: nginx-core Version: 1.13.x
Keywords: Cc:
uname -a: 2.6.32
nginx -V: nginx version: nginx/1.12.2 built by gcc 4.8.2 (GCC) built with OpenSSL 1.0.2h 3 May 2016 TLS SNI support enabled

Description

1, resolver would not down when it fails, and would use it when next resolve
2, Nginx would not retry when one resolver fails

Why?

Change History (2)

in reply to:  description comment:1 by crasyangel.lhy@…, 7 years ago

Replying to crasyangel.lhy@…:

1, resolver would not down when it fails, and would use it when next resolve
2, Nginx would not retry when one resolver fails

Why?

Config:

resolver 127.0.0.1 172.18.254.4;
resolver_timeout 2s;

Upstream or other caller can retry if resolver do not

comment:2 by Maxim Dounin, 7 years ago

Resolution: → wontfix
Status: new → closed

The resolver_timeout directive controls hard limit on the total DNS resolution time. If not answered, DNS queries are resent (to a different server if configured) each 5 seconds, see here. There is no way to configure this timeout though, as this doesn't seem to be needed in most cases in practice.

To make sure DNS queries are resent to a different server if one the configured servers is down, consider using resolver_timeout set to something like 6s or more.

Note: See TracTickets for help on using tickets.