Bug 15922
Summary: | Problems with bind and caching-nameserver | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | John William <jw2357> |
Component: | bind | Assignee: | Bernhard Rosenkraenzer <bero> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-08-10 14:26:43 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John William
2000-08-10 14:25:23 UTC
Can't reproduce this... If it's only after a prolonged uptime, maybe running "ndc reload" every couple of days from cron helps you? I'm sorry you couldn't reproduce it, but I am not the only person having this problem so I know it isn't just me. I have verified everything is installed correctly with "rpm -V" on the bind and caching-nameserver packages so nothing has modified the out-of-the-box settings. The problem seems to take 3-5 days on my test server before cropping up, but it is easily reproducable here. Reloading/restarting named doesn't work. Once named gets into a "mood" the process has to be killed to restore normal operation. And once the problem starts, it seems to quickly spread to affect all lookups from any machine except the host. On the host everything works fine. |