I see this message consistently upon resume from suspend (sleep). It is usually followed by a reload of the config file, and, perhaps depending on the number of poke messages, perhaps not, other tasks which depend on DNS being up may have trouble until it is finished with the reload. In my case I have 'ddclient' configured with the canonical address of a site to report the IP address of the system, but it fails because the name resolution request fails. Here are the relevant messages from the log:
Apr 15 18:34:14 hostname acpid: client connected from 3055[0:0] Apr 15 18:34:14 hostname acpid: 1 client rule loaded Apr 15 18:34:15 hostname named[1767]: *** POKED TIMER *** Apr 15 18:34:15 hostname named[1767]: *** POKED TIMER *** Apr 15 18:34:15 hostname named[1767]: *** POKED TIMER *** Apr 15 18:34:15 hostname named[1767]: *** POKED TIMER *** Apr 15 18:34:15 hostname named[1767]: *** POKED TIMER *** Apr 15 18:34:15 hostname ddclient[2303]: WARNING: cannot connect to www.whatismyip.com:80 socket: IO::Socket::INET: Bad hostname 'www.whatismyip.com' Apr 15 18:34:15 hostname XXXsyslog_triggered_scriptXXX: WAN link disconnected or IP address reset, all sessions killed. Apr 15 18:34:19 hostname named[1767]: received control channel command 'reconfig' Apr 15 18:34:19 hostname named[1767]: loading configuration from '/etc/bind/named.conf' Apr 15 18:34:19 hostname named[1767]: reading built-in trusted keys from file '/etc/bind/bind.keys' Apr 15 18:34:19 hostname named[1767]: using default UDP/IPv4 port range: [1024, 65535] Apr 15 18:34:19 hostname named[1767]: using default UDP/IPv6 port range: [1024, 65535] Apr 15 18:34:19 hostname named[1767]: set up managed keys zone for view _default, file 'managed-keys.bind' Apr 15 18:34:19 hostname named[1767]: reloading configuration succeeded Apr 15 18:34:19 hostname named[1767]: any newly configured zones are now loaded The workaround is to configure ddclient to contact an IP address but it seems like there should be a more elegant handling of the order things are brought up, or some notification of where the named reload is coming from. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
