Re: Very long delays, is it just djbdns?

On Sat, 13 Nov 2010 07:19:39 +0000
Sabahattin Gucukoglu <[email protected]> wrote:

> Try this command from a nice, clean dnscache:
> host -v 2001:470:1f09:103e::2354
> 
> It took me three tries on my fastest, most well-connected machine to
> get the NXDOMAIN response.  I haven't got to the bottom of it yet,
> but if anybody has a clue, please do share!

ipv6 is not mature yet I'd say. That's why I added:

.xaq.nl:127.0.0.1:localhost.xaq.nl:259200
.ip6.arpa::localhost.xaq.nl:259200
^*.ip6.arpa:ipv6.reverse.xaq.nl:7200

to my local tinydns on 127.0.0.1 and added:

echo 127.0.0.1 > /service/dnscache/root/servers/ip6.arpa

and reset your dnscache:

svc -t /service/dnscache

Ok, I get bogus responses, that's true, but I always get a response and
it only takes milliseconds ;)

(I run an ipv6 patched version of tinydns):

$ dnsip6 ipv6.google.com
2a00:1450:8003::63 

$ dnsname 2a00:1450:8003::63
ipv6.reverse.xaq.nl

After a clear cache:

$ time dnsname 2a00:1450:8003::63
ipv6.reverse.xaq.nl

real    0m0.004s
user    0m0.000s
sys     0m0.000s

R.

R.

-- 
___________________________________________________________________
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+------------------------------------------------------------------+
| Richard Lucassen, Utrecht                                        |
| Public key and email address:                                    |
| http://www.lucassen.org/mail-pubkey.html                         |
+------------------------------------------------------------------+