IPv6 DNS Caching?

[badcrc]

I am running a Ubuntu 8.10 Linux server in my house. I have it setup to give every client a IPv4 and IPv6 address upon connecting to my network. Curious though, is it possible to do local IPv6 DNS caching? I use pdnsd[1] as my LAN's DNS server, which supports both IPv4 and IPv6 at the same time. It is currently setup to utilize OpenDNS[2], Comcast Seattle and the old Verizon DNS servers, which works great for IPv4 addressing. I want to offer the same local DNS caching for IPv6 address on my server to my LAN clients. What addresses would I use for recursing DNS lookups? I am tunneling through a HE Seattle, WA server.

[1]: http://www.phys.uu.nl/~rombouts/pdnsd/
[2]: http://www.opendns.com/

[malfeasant]

Just an aside about OpenDNS, you might want to consider using something else.  OpenDNS tends to return an address of it's own server, then proxy your requests to the real servers.  Personally, I see this as a potential privacy invasion.  They don't seem to do this with every website, but certain select ones- like google.  It is certainly conceivable that any unsecured site such as certain webmail could be proxied too- even if OpenDNS doesn't have any nefarious plans, they would be an attractive target for crackers.

[piojan]

HE has some recursive dns. The addreses are somewhere on the forum.
Howevere there is no need for that.
If a client askes you dns over ipv6 for a record like (a or aaaa), your dns will give an answer.
Probably the fastest option is if it (your dns) would use ipv4 but it is completelty separet form the client side.

[ericj]

HE has some recursive dns. The addreses are somewhere on the forum.

The servers that listen on IPv6 are:
ns1.fmt.he.net (2001:470:0:470::470)
ns2.fmt.he.net (2001:470:0:471::471)
ns1.sjc.he.net (2001:470:0:472::472)
ns1.fmt2.he.net (2001:470:0:473::473)

[tb0hdan]

HE has some recursive dns. The addreses are somewhere on the forum.

The servers that listen on IPv6 are:
ns1.fmt.he.net (2001:470:0:470::470)
ns2.fmt.he.net (2001:470:0:471::471)
ns1.sjc.he.net (2001:470:0:472::472)
ns1.fmt2.he.net (2001:470:0:473::473)

Hi there.

None of those work for me. I have both HE and Sixxs tunnels.

Here are two mine ( both on co-location ):

2001:15c0:65ff:235::2
2001:15c0:65ff:25b::2

Both are recursive for IPv6 users ( including Teredo ).

Choose one that has better performance / lower latency.


Have fun!

[broquea]

Those caching NS are only usable by our colo customers.
Our tunnel users would want to use the anycasted NS listed inside our broker interface. Same would be true with the Sixxs NS they provide for their tunnel users.