Baoyuantop commented on issue #13082:
URL: https://github.com/apache/apisix/issues/13082#issuecomment-4036044494

   APISIX employs two independent DNS resolution mechanisms with different 
timeout configurations that do not interfere with each other:
   
   The Nginx-level resolver (controlled by the `resolver_timeout` 
configuration) is primarily responsible for scenarios where Nginx itself needs 
to resolve domain names. This mechanism only affects Nginx's native `resolver` 
directives, used for internal Nginx domain name resolution (e.g., when using 
`proxy_pass` to resolve a domain name to an upstream). The timeout is 
controlled by `resolver_timeout`.
   
   The APISIX Lua-level DNS client (hardcoded 2000ms) is primarily responsible 
for all scenarios where APISIX needs to actively resolve domain names to IP 
addresses during request processing. The timeout is hardcoded in the code.
   
   Could you describe your use case? Why is it necessary to modify this 
configuration?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to