diff options
author | Internet Software Consortium, Inc <@isc.org> | 2007-09-07 14:14:04 -0600 |
---|---|---|
committer | LaMont Jones <lamont@debian.org> | 2007-09-07 14:14:04 -0600 |
commit | 30bca935d5d0e0b54328f79de1af5e6b16e9d507 (patch) | |
tree | fcfd41daa51418856fd9caab4acab9f72e87287c /FAQ | |
parent | 643dff150d15513d757061a99d9e8f9678fc007f (diff) | |
download | bind9-30bca935d5d0e0b54328f79de1af5e6b16e9d507.tar.gz |
9.2.0rc4
Diffstat (limited to 'FAQ')
-rw-r--r-- | FAQ | 15 |
1 files changed, 8 insertions, 7 deletions
@@ -65,12 +65,13 @@ A: This is often caused by TXT records with missing close quotes. Check that all TXT records containing quoted strings have both open and close quotes. -Q: How do I produce a usable core file from a multithreaded named -on Linux? +Q: How do I produce a usable core file from a multithreaded named on Linux? -A: Apply the kernel patch found in bind9/linux/coredump-patch and rebuild -the kernel. This patch causes multithreaded programs to dump the correct -thread. +A: If the Linux kernel is 2.4.7 or newer, multithreaded core dumps +are usable (that is, the correct thread is dumped). Otherwise, if using +a 2.2 kernel, apply the kernel patch found in contrib/linux/coredump-patch +and rebuild the kernel. This patch will cause multithreaded programs to dump +the correct thread. Q: How do I restrict people from looking up the server version? @@ -144,7 +145,7 @@ Q: I keep getting log messages like the following. Why? Jun 21 12:00:00.000 client 10.0.0.1#1234: update denied -Someone is trying to update your DNS data using the RFC2136 Dynamic +A: Someone is trying to update your DNS data using the RFC2136 Dynamic Update protocol. Windows 2000 machines have a habit of sending dynamic update requests to DNS servers without being specifically configured to do so. If the update requests are coming from a Windows 2000 machine, @@ -156,7 +157,7 @@ Q: I see a log message like the following. Why? couldn't open pid file '/var/run/named.pid': Permission denied -You are most likely running named as a non-root user, and that user +A: You are most likely running named as a non-root user, and that user does not have permission to write in /var/run. The common ways of fixing this are to create a /var/run/named directory owned by the named user and set pid-file to "/var/run/named/named.pid", or set |