[148154] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: IPv6 resolvers

daemon@ATHENA.MIT.EDU (Raymond Dijkxhoorn)
Wed Jan 4 15:21:55 2012

Date: Wed, 4 Jan 2012 21:21:05 +0100 (CET)
From: Raymond Dijkxhoorn <raymond@prolocation.net>
To: Seth Mos <seth.mos@dds.nl>
In-Reply-To: <EBA25509-B69D-41BD-86F4-04EFABBA53A1@dds.nl>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Hi!

> But I was wondering if a more permanent solution for these resolvers exist.
>
> 74.82.42.42	 2373 msec
> 2001:470:20::2	 2592 msec
>
> The google DNS server I'm using is doing swimmingly so far, OpenDNS seems ok too.
> 2001:4860:4860::8844	 16 msec

[root@ipv6proxy ~]# ping 74.82.42.42
PING 74.82.42.42 (74.82.42.42) 56(84) bytes of data.
64 bytes from 74.82.42.42: icmp_seq=1 ttl=61 time=0.664 ms
64 bytes from 74.82.42.42: icmp_seq=2 ttl=61 time=0.640 ms
64 bytes from 74.82.42.42: icmp_seq=3 ttl=61 time=0.551 ms
64 bytes from 74.82.42.42: icmp_seq=4 ttl=61 time=0.614 ms

[root@ipv6proxy ~]# ping6 2001:470:20::2
PING 2001:470:20::2(2001:470:20::2) 56 data bytes
64 bytes from 2001:470:20::2: icmp_seq=1 ttl=61 time=0.488 ms
64 bytes from 2001:470:20::2: icmp_seq=2 ttl=61 time=0.478 ms
64 bytes from 2001:470:20::2: icmp_seq=3 ttl=61 time=0.739 ms
64 bytes from 2001:470:20::2: icmp_seq=4 ttl=61 time=0.515 ms

Looks pretty normal here.

Bye,
Raymond.


home help back first fref pref prev next nref lref last post