From: "Robert Waldner" <[EMAIL PROTECTED]> > Can your DNS-forwarder resolve reverse-dns for your internal IPs? > Reverse-lookup is the most likely candidate for delays I can think of.
I agree. I solved this all with djbdns but it is convoluted. I created two aliased IPs on my internal interface (you really only need one but I found two simpler for other reasons). tinydns runs on ...161 and serves my internal IPs only. dnscache runs on ...160 and forwards internet IPs and my internal IPs. All interior boxes are configured to use ...160 as the dns server. # configure tinydns to serve my internal IPs tinydns-conf tinydns dnslog /etc/tinydns ....161 # dns ./add-ns parrotchat.net ....161 # dns ./add-ns 168.....in-addr.arpa ....161 # dns ./add-host ... # configure dnscache to forward external IPs and cache my internal IPs dnscache-conf dnscache dnslog /etc/dnscache ....160 # dnsx ... cd /service/dnscache/root/servers/ echo ....161 > parrotchat.net # 161=dns echo ....161 > 168.....in-addr.arpa # 161=dns # Note: modify clients to use ....160 # dnsx
