nginx on Debian: dynamic network interfaces

B.R. reallfqq-nginx at
Wed May 27 07:51:40 UTC 2015

The keyword here is 'dynamic'.

I even modified the service configuration to depend on 'named', but the
thing is that being dynamic, the network and name resolution dependency
might be fulfilled while the actual service is not ready yet. Those
dependencies might (dis)appear following this 'hot-plug' behavior and
services should adapt to this.
'auto' (synchronous) differs from 'hot-plug' (asynchronous).

Is there really nothing you can do on your side about it?
It is a little tiresome to see both parts throwing the ball back.

*B. R.*

On Tue, May 26, 2015 at 7:11 PM, Maxim Dounin <mdounin at> wrote:

> Hello!
> On Tue, May 26, 2015 at 05:53:00PM +0200, B.R. wrote:
> > Hello,
> >
> > Facing issues on Debian with official nginx packages, I filled a bug up
> on
> > the Debian tracker which ended up as being closed since Debian refers to
> > the faulty service(s), nginx being one.
> >
> > ​Bug #785253 <>​
> >
> > ​I could not fill a bug on since OAuth 2.0
> > authentication through Google went away (already adressed in a separated
> > thread).
> >
> > Could someone here confirms nginx (and not the OS) is to be adressed?
> Looking though the bug in question I don't see anything to fix in
> nginx.  As far as I understand the problem, it is as follows:
> 1. you are trying to start nginx without access to DNS;
> 2. your nginx configuration contains DNS names and therefore
>    requires access to DNS for nginx to start, as nginx resolves
>    DNS names on startup;
> You should either configure your OS to ensure that you start nginx
> after DNS is available or change your nginx configuration to avoid
> DNS names.
> --
> Maxim Dounin
> _______________________________________________
> nginx mailing list
> nginx at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nginx mailing list