Bug 159451
Summary: | Bind Seems to hang for a few seconds...randomly | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | CDapplications <info> |
Component: | bind | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED NOTABUG | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | ||
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: | 2005-06-03 16:34:56 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
CDapplications
2005-06-02 19:17:38 UTC
You may not have port 53 blocked on your machine, but are you positive nothing in the path between your machine and some root nameservers has port 53 blocked ? (NOTE: it is typical ISP behaviour to block this port to all but their own nameservers). Are you using NetworkManager ? Do you have SELinux enabled ? Can you reproduce the timeout with options { ... query-source port 53; ... }; in /etc/named.conf ? If so, please try to reproduce the problem with debugging / tracing enabled - please run these commands: tcpdump -vvv -nl -i any -s 2048 port domain 2>&1 | tee /tmp/tcpdump.log & . /etc/sysconfig/named; touch ${ROOTDIR}/var/named/named.run; chown named:named ${ROOTDIR}/var/named/named.run; rndc trace 99; and then reproduce the problem. When you have reproduced it: pkill tcpdump rndc trace 0 and append the /tmp/tcpdump.log and $ROOTDIR/var/named/named.run files to this bug report. Your named.conf and zone files if any would also be most useful in tracking down the problem. I've not been able to reproduce this problem with bind-9.2.5 on FC-3, both behind a firewall and on external internet, in forward or authoritative modes, with SELinux disabled or enabled, so further information is required to diagnose this problem. Hello Jason. What a shame on me... In fact, after many questions asked, since monday, to the datacenter hosting the servers and many answers given : 'it is not our network, it your server...', I looked at all the solutions possible on the software side. But the solution came last night...a switch failed putting all their network down for more than 3 hours. The cause of the timeout is (i presume) this switch that was already showing signs of fatigue. Now, I don't have any time out anymore. Sorry for the time you spent answering my bug. Anyway I would like to thank you a lot. Regards, Christophe No problem - closing out . |