hoopycat wrote:
You don't need them as a necessary condition of using IPv6. IPv6 is just a transport layer for DNS, and whether or not you use IPv6 to query DNS will not impact the results of the query(*).
The reason the IPv6 resolvers don't appear there is because DHCPv4 is used to populate /etc/resolv.conf automatically, and it doesn't know about the IPv6 resolvers. You are more than welcome to disable DHCP and use a static network configuration, which will let you do whatever you want with /etc/resolv.conf.
(*) For pedants: We'll assume all the DNS servers involved neglect the source IP address of the query when deciding which records to return. That's true in this case.
Thanks for the help! I'm using static networking actually. While we're on the subject, can you tell me if my /etc/network/interfaces file looks correct? I'm running Debian 6. I added in IPv6 support, but I'm not sure if I did it correctly.
Code:
# localhost
auto lo
iface lo inet loopback
# eth0 interface
auto eth0 eth0:0
# public
iface eth0 inet static
address [Linode IPv4 IP]
netmask 255.255.255.0
gateway [Linode IPv4 Gateway IP]
# private
iface eth0:0 inet static
address [Linode IPv4 Private IP]
netmask 255.255.128.0
# IPv6
iface eth0 inet6 static
pre-up modprobe ipv6
address [Linode IPv6 IP]
up echo 0 > /proc/sys/net/ipv6/conf/all/autoconf
netmask 64
gateway fe80::1
After restarting, I noticed /proc/sys/net/ipv6/conf/all/autoconf was still set to 1 instead of 0. `ping6 fe80::1` also doesn't seem to work? But I'm able to `ping6 ipv6.google.com` just fine. Here's the output of `ip -6 address show eth0`:
Code:
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 [Linode IPv6 IP]/64 scope global dynamic
valid_lft 43199sec preferred_lft 43199sec
inet6 [Linode IPv6 Link-Local IP]/64 scope link
valid_lft forever preferred_lft forever