Thanks to all for your input.

@Konstantin
'workaround' has a very specific meaning there is a bug and a way to avoid
it.
I want to address the bug where it lies, the latter being unclear still.
systemd has probably benefits and some drawbacks which are important to me:
I am sticking to sysvinit.

@Francis
Thanks for your input.
I know that not using names meanings name resolution won't be needed.
However cutting in features works around bugs, meaning there is one.
DNS has been invented because of many difficulties involved when you use IP
addresses: using names in a configuration, especially for an external
resolver over which I do not have control is the way to go.
I do not want to make breakable configurations simply because my OS and one
service does not understand each other.
I made all that fuss and I am spending my time to identify a bug and
address it.
FYI, using the old 'auto' (synchronous) mode on the network service is also
a workaround, which seems more reliable to me. I do not want to stick with
this since the OS default is to use 'hotplug'. That is a workaround... I
want the chase the bug. (Am I repeating myself? ;o) )

@Maxim
I understand from your words that using hotplug interfaces is currently not
supported by nginx (as I observed).
Now there are (at least) 2 ways of seing it:
1°) Considering the asynchronous nature of the new default network
configuration of Debian, the services should adapt to handle cases where
the network is 'not really up' or some features are missing (no IP address
bound, name resolution not working) --> Debian's stance, making nginx
service faulty
2°) The network should be up when (and only when) it is advertised so,
making the services dependencies on system facilities reliable and safe -->
Debian OS is faulty
Removing features because 'it does not work' is in no way a solution to my
eyes.

There might have huge divergence on how to embrace things, but if Debian's
claims on the fact service should have proper support are right and {if you
disagree with the way Debian has taken or you do not want to change your
way}, you shall then declare yourself not supporting the Debian distro.

@itpp2012
I love your way of 'simplifying' things.
I probably differ on the definition, since to me 'simpler' converges
towards 'standard' and/or 'default'.
Making scripts is one of the multiple workarounds, but that is definitely
not the solution. Will you make everyone using nginx on Debian using that
trick, as soon as they need DNS on a default 'hotplug' interface with
sysvinit?
---
*B. R.*

On Wed, May 27, 2015 at 3:53 PM, itpp2012 <nginx-forum@nginx.us> wrote:

> B.R. Wrote:
> -------------------------------------------------------
> > 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
>
> Why not simplify things, set nginx start to manual, create a service that
> runs a script, inside that script attempt to resolve some dns name, when it
> fails wait a while and loop back, when it succeeds start nginx and exit
> script.
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,259137,259175#msg-259175
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx