Bug 50164
Summary: | Bind bind-8.2.3-0.6.x problem | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <mal> |
Component: | bind | Assignee: | Bernhard Rosenkraenzer <bero> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
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: | 2003-08-01 19:06:09 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
Need Real Name
2001-07-27 16:16:52 UTC
This is a link to that old bug: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=10479 This looks like the uplink DNS (clickxchange.com) was down, the result "domain doesn't exist" got cached, and was looked up from the cache later - in that case, it should work again a day later. Could this be the problem? I do not think that this was the cause because dig www.clickxchange.com a took several seconds to reply. If it were cached it would reply right away. For all cached domains the DNS at 192.168.3.1 replies with no any delay. Also, in the response from dig www.clickxchange.com a there was a string having "Connection timed out" ;; res_nsend to server default -- 192.168.3.1: Connection timed out which seems means that caching DNS at 192.168.3.1 did not send a response in specific time period. |