Using:
resolver 127.0.0.1 valid=300s;
Does not work. I assume this would simply uses the DNS servers listed in
/etc/resolv.conf? Thanks.
Posted at Nginx Forum:
Using:
resolver 127.0.0.1 valid=300s;
Does not work. I assume this would simply uses the DNS servers listed in
/etc/resolv.conf? Thanks.
Posted at Nginx Forum:
On 20 December 2013 23:20, justin [email protected] wrote:
Using:
resolver 127.0.0.1 valid=300s;
Does not work. I assume this would simply uses the DNS servers listed in
/etc/resolv.conf?
Your assumption is wrong. You’d need to be running a local DNS
resolver for that config to work.
On 12/20/2013 3:20 PM, justin wrote:
Using:
resolver 127.0.0.1 valid=300s;
Does not work. I assume this would simply uses the DNS servers listed in
/etc/resolv.conf? Thanks.
The resolver directive tells NSD to do its own DNS lookups, bypassing
the system name lookup call (and thus /etc/resolv.conf) entirely.
On Fri, Dec 20, 2013 at 04:12:45PM -0800, Darren P. wrote:
On 12/20/2013 3:20 PM, justin wrote:
Using:
resolver 127.0.0.1 valid=300s;
Does not work. I assume this would simply uses the DNS servers listed in
/etc/resolv.conf? Thanks.The resolver directive tells NSD to do its own DNS lookups, bypassing
the system name lookup call (and thus /etc/resolv.conf) entirely.
That’s not quite true. Resolving that takes place during
configuration parsing uses the system resolver. Resolving
that takes place at run time uses the DNS servers from the
“resolver” directive. Please see Module ngx_http_core_module
and Module ngx_http_ssl_module for details.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs