Here is another issue: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=143786 This one specifically addresses the named daemon not restarting (which is a broken bind-9.2.4-5_EL3, not caching-nameserver)... it also says that they will not be fixing the caching-nameserver issue, because it is not a bug, it is by design.
[Centos] bind and 3.4
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: [Centos] bind and 3.4
- From: mailing-lists at hughesjr.com (Johnny Hughes)
- Date: Wed Jan 12 16:06:00 2005
- In-reply-to: <Pine.LNX.4.44.0501121507160.25524-100000@xxxxxxxxxxxxxx>
- References: <34232.192.156.88.85.1105542174.squirrel@xxxxxxxxxxxxxxxxx> <Pine.LNX.4.44.0501121507160.25524-100000@xxxxxxxxxxxxxx>
- Follow-Ups:
- [Centos] bind and 3.4
- From: Lance Davis
- [Centos] bind and 3.4
- References:
- [Centos] bind and 3.4
- From: Johnny Hughes
- [Centos] bind and 3.4
- From: Lance Davis
- [Centos] bind and 3.4
- Prev by Date: [Centos] bind and 3.4
- Next by Date: [Centos] Modprobe errors during startup on CentOS 3.4
- Previous by thread: [Centos] bind and 3.4
- Next by thread: [Centos] bind and 3.4
- Index(es):
 |