Hello, I got the following in my kern.log: May 13 11:57:59 kernel: [ 17.282032] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready May 13 11:57:59 kernel: [ 17.539625] RPC: Registered named UNIX socket transport module. May 13 11:57:59 kernel: [ 17.539629] RPC: Registered udp transport module. May 13 11:57:59 kernel: [ 17.539630] RPC: Registered tcp transport module. May 13 11:57:59 kernel: [ 17.539631] RPC: Registered tcp NFSv4.1 backchannel transport module. May 13 11:57:59 kernel: [ 17.559571] FS-Cache: Loaded May 13 11:57:59 kernel: [ 17.576270] FS-Cache: Netfs 'nfs' registered for caching May 13 11:57:59 kernel: [ 17.621693] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). May 13 11:58:01 kernel: [ 20.074827] bnx2 0000:02:00.0 eth0: NIC Copper Link is Up, 1000 Mbps full duplex May 13 11:58:01 kernel: [ 20.074833] May 13 11:58:01 kernel: [ 20.074950] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
but then I get an emergency error for my nginx service: 2015/05/13 11:58:02 [emerg] 1901#0: host not found in resolver "ns0.fdn.org" in /etc/nginx/nginx.conf:58 Here is my /etc/resolv.conf content: nameserver 62.210.16.6 nameserver 62.210.16.7 search online.net The network is up (it is a dependency of my nginx service), my service has been reinstalled with insserv (previously set up with update-rc.d). However, for an unknown reason, at the time nginx tries to resolv the external nameserver, it fails. If I start the service manually later, it works. If I resolve manually the nameserver later, it also works: dig @62.210.16.6 ns0.fdn.org [...] ;; ANSWER SECTION: ns0.fdn.org. 41585 IN A 80.67.169.12 What could be the problem? How should I investigate this? Thanks, --- *B. R.*
