Scott wrote on Wed, Jul 24, 2002 at 03:55:44PM -0400 : > Should I be using caching nameserver on this box?
It could help. What is happening is the server on your machine is doing a reverse lookup on the IP address of the machine that is connecting to it. Do you understand what the problem is? The problem is only partially able to be fixed by a proper dns configuration on your part. The other part is that someone else's DNS out on the internet can be royally screwed and you will still see the delays. But that doesn't sound like your problem. It sounds like you are having problems with reverse lookups from local connections. You should have a DNS server setup on your local lan that is authoritative for the domain name you are using *AND* the local IP subnet (reverse). So if you were using *.domain.com and 192.168.1.*, then your dns server should be authoritative for domain.com and 1.168.192.in-addr.arpa. > It is not hosting DNS. What are you using as a DNS source? Your ISP? Where is the connection originating from? What's their IP address? The answers to those questions provide a lot of direction to the one answer that will solve all of your problems. Blue skies... Todd -- Todd Lyons -- MandrakeSoft, Inc. http://www.mandrakesoft.com/ UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn Cooker Version mandrake-release-9.0-0.2mdk Kernel 2.4.18-21mdk
msg56517/pgp00000.pgp
Description: PGP signature
