# Resolver for upstream

**URL:** <https://www.ruby-forum.com/t/resolver-for-upstream/230582>\
**Category:** NGINX\
**Created:** [June 25, 2014, 2:19am UTC](https://www.ruby-forum.com/t/resolver-for-upstream/230582 "2014-06-25T02:19:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jason\_sam](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/7993a0/32.png) [@jason\_sam](https://www.ruby-forum.com/u/jason_sam)\
**Post date:** [June 25, 2014, 2:19am UTC](https://www.ruby-forum.com/t/resolver-for-upstream/230582/1 "2014-06-25T02:19:15Z")

</div>

We are trying to use resolver on upstream. It is not working for some  
reason. We are using nginx 1.6.0. Supposedly the feature should be  
available  
on 1.5.12.

When we try to use it, It always give us an error. nginx: [emerg]  
invalid  
parameter “resolve” in… And when I checked the source code, it doesn’t  
look like the feature was in there.

According to upstream documentation it should work like this:  
resolve  
monitors changes of the IP addresses that correspond to a domain name of  
the  
server, and automatically modifies the upstream configuration without  
the  
need of restarting nginx (1.5.12).  
In order for this parameter to work, the resolver directive must be  
specified in the http block. Example:

http {  
resolver 10.0.0.1;

```
upstream u {
    zone ...;
    ...
    server example.com resolve;
}

```

}

Posted at Nginx Forum:

> **[resolver for upstream](https://forum.nginx.org/read.php?2,251138,251138#msg-251138)**
>
> We are trying to use resolver on upstream. It is not working for some reason. We are using nginx 1.6.0. Supposedly the feature should be available on 1.5.12. When we try to use it, It always give us an error. nginx: \[emerg\] invalid parameter...

---

<div class="post-metadata">

**Author:** ![badtzhou](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/a6a055/32.png) [@badtzhou](https://www.ruby-forum.com/u/badtzhou)\
**Post date:** [June 25, 2014, 2:33am UTC](https://www.ruby-forum.com/t/resolver-for-upstream/230582/2 "2014-06-25T02:33:01Z")

</div>

Hello!

On Tue, Jun 24, 2014 at 08:18:04PM -0400, badtzhou wrote:

> monitors changes of the IP addresses that correspond to a domain name of the  
> server, and automatically modifies the upstream configuration without the  
> need of restarting nginx (1.5.12).  
> In order for this parameter to work, the resolver directive must be  
> specified in the http block. Example:

You’ve missed this part above it:

: Additionally, the following parameters are available as part of  
: our commercial subscription:

> **[Module ngx\_http\_upstream\_module](http://nginx.org/en/docs/http/ngx_http_upstream_module.html#server)**
>
> The ngx\_http\_upstream\_module module is used to define groups of servers that can be referenced by the proxy\_pass, fastcgi\_pass, uwsgi\_pass, scgi\_pass, memcached\_pass, and grpc\_pass directives.

–  
Maxim D.

> **[nginx](http://nginx.org/)**

---

<div class="post-metadata">

**Author:** ![badtzhou](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/a6a055/32.png) [@badtzhou](https://www.ruby-forum.com/u/badtzhou)\
**Post date:** [July 2, 2015, 10:49am UTC](https://www.ruby-forum.com/t/resolver-for-upstream/230582/3 "2015-07-02T10:49:13Z")

</div>

I have encountered such a problem

Posted at Nginx Forum:

> **[Re: resolver for upstream](https://forum.nginx.org/read.php?2,251138,260017#msg-260017)**
>
> We are trying to use resolver on upstream. It is not working for some reason. We are using nginx 1.6.0. Supposedly the feature should be available on 1.5.12. When we try to use it, It always give us an error. nginx: \[emerg\] invalid parameter...