Linux - Server This forum is for the discussion of Linux Software used in a server related context. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
06-02-2011, 08:10 PM
|
#1
|
Member
Registered: Mar 2008
Distribution: slackware
Posts: 175
Rep:
|
how to force nginx to do DNS lookups
Does anyone know if there is a way to get nginx to perform DNS lookups at regular intervals against hostnames that are defined for upstream servers? It seems nginx only performs a DNS lookup once, the first time it starts, and subsequently does not perform any other DNS lookups. This causes problems when the ip addresses of our upstream servers change.
I posted this same question in the nginx forum; however I also posted it here as it seems that not many of the posts there get answered.
http://forum.nginx.org/read.php?15,203481
|
|
|
06-03-2011, 03:42 AM
|
#2
|
LQ Guru
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,220
|
Hi,
I guess you can use in nginx.conf
where x.x.x.x is the IP of a dns server that is aware of the changes in the upstream servers IPs.
Regards
|
|
|
06-03-2011, 11:43 AM
|
#3
|
Member
Registered: Mar 2008
Distribution: slackware
Posts: 175
Original Poster
Rep:
|
Thanks for the suggestion but I already tried that and it doesn't change the behavior. It only sets the nameserver nginx queries the first time it is started.
|
|
|
06-05-2011, 04:47 AM
|
#4
|
LQ Guru
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,220
|
Yes, but according to Igor Sysoev (nginx author), cache should expire every 5 mins. See this post on the matter.
So unless upstream servers change ip addresses in less that 5 mins, you should not have a problem.
|
|
|
06-05-2011, 10:12 PM
|
#5
|
Member
Registered: Mar 2008
Distribution: slackware
Posts: 175
Original Poster
Rep:
|
Thanks. His post in your link does seem to suggest that the cache expires after 5 mins but that is definitely not the case.
|
|
|
06-06-2011, 01:43 AM
|
#6
|
LQ Guru
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,220
|
Are you sure it's not the resolver you're using, that is not aware of the IP changes of the upstream servers?
You may install a lightweight resolver (like dnsmasq) locally and tune its cache to your liking
Regards
|
|
|
06-06-2011, 02:01 AM
|
#7
|
Member
Registered: Mar 2008
Distribution: slackware
Posts: 175
Original Poster
Rep:
|
Yes I'm 100 percent sure it's not the resolver. This is how nginx works, at least by default.
|
|
|
All times are GMT -5. The time now is 12:55 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|