Red Hat Bugzilla – Bug 80228
after suspend/wake up, named no longer responds
Last modified: 2015-01-07 19:02:33 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
After I suspend my laptop and wake it back up, the local caching name server
stops responding. I suppose this has to do with the fact that the network
interfaces are restarted, and named doesn't realize it would have to bind to the
ports of the new interfaces. Restarting it fixes the problem, but just reload
doesn't. Perhaps we should condrestart it on wake up?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Verify that named is running, and is used to resolve names
4.Try to resolve names
Actual Results: It fails
Expected Results: It should work
This is not new in the beta, but it'd never occurred to me to report it.
This should be fixed with 3.0.2-19, by changing services to start *after* the
network, not before.
Confirmed fixed in rawhide, sorry about the long delay.