| Author |
Message |
Xangis
Joined: 07 May 2009
Posts: 3
Location: Columbus, OH
|
| Posted: Fri Jan 22, 2010 11:19 am Post subject: IPv6 Linode DNS AAAA Record Setup |
|
|
I'm using the Linode DNS manager for my domains. I just added IPv6 support to my server using Hurricane Electric and can ping IPv6 addresses.
I want to set up an AAAA DNS record for my server in the DNS manager, but can't get it to take. It's probably some newbie mistake. Here's my HE config:
Code: Global Tunnel ID: 47007 Local Tunnel ID: 460
Description:
Registration Date: Fri, Jan 22, 2010
Tunnel Endpoints
Server IPv4 address: 209.51.161.58
Server IPv6 address: 2001:470:4:1cc::1/64
Client IPv4 address: 72.14.188.42
Client IPv6 address: 2001:470:4:1cc::2/64
Available DNS Resolvers
Anycasted IPv6 Caching Nameserver: 2001:470:20::2
Anycasted IPv4 Caching Nameserver: 74.82.42.42
Routed IPv6 Prefixes and rDNS Delegations
Routed /48: Allocate /48
Routed /64: 2001:470:5:1cc::/64
RDNS Delegation NS1: none
RDNS Delegation NS2: none
RDNS Delegation NS3: none
I've tried both the client IPv6 address and the server IPv6 address, and the DNS manager tells me they are not a valid IPv4 or IPv6 address, so what should I be using? |
|
| Back to top |
|
hoopycat
Joined: 30 Aug 2008
Posts: 1294
Location: Rochester, New York
|
| Posted: Fri Jan 22, 2010 12:10 pm Post subject: |
|
|
Are you entering the netmask (/64)? As with IPv4 addresses, that's only needed for interface configuration; don't include it in DNS records.
Also, the Server and Client IP addresses are for the actual point-to-point link between you and HE... if you want to set up reverse DNS or use multiple IPv6 addresses, make sure to add an IP from the Routed /64 to eth0 and use that. |
|
| Back to top |
|
jed
Joined: 28 Mar 2009
Posts: 394
Location: New Jersey
|
| Posted: Fri Jan 22, 2010 1:21 pm Post subject: |
|
|
hoopycat has your answer.
Additionally, I'd like to inject my spiel about not using your point-to-point address as a routed IP address on your Linode, given that HE does not permit you to alter your rDNS (they're discouraging you from using this address).
I recommend assigning something out of your routed /64 to your Linode as its communication address and keep the point-to-point address limited to your tunnel configuration. |
|
| Back to top |
|
Xan
Joined: 08 Feb 2004
Posts: 562
Location: Austin
|
| Posted: Sat Jan 23, 2010 12:50 am Post subject: |
|
|
| You know what would be really neat, Jed... Native IPv6 on Linode. :-) |
|
| Back to top |
|
OverlordQ
Joined: 04 Jun 2004
Posts: 312
|
| Posted: Sat Jan 23, 2010 2:44 am Post subject: |
|
|
jed wrote: hoopycat has your answer.
Additionally, I'd like to inject my spiel about not using your point-to-point address as a routed IP address on your Linode, given that HE does not permit you to alter your rDNS (they're discouraging you from using this address).
I recommend assigning something out of your routed /64 to your Linode as its communication address and keep the point-to-point address limited to your tunnel configuration.
Idiots guide for that? |
|
| Back to top |
|
hoopycat
Joined: 30 Aug 2008
Posts: 1294
Location: Rochester, New York
|
| Posted: Sat Jan 23, 2010 7:46 am Post subject: |
|
|
From my /etc/network/interfaces:
Code: iface eth0 inet6 static
address 2001:470:1f07:f41::dead:beef
netmask 64
, with 2001:470:1f07:f41::/64 being within my Routed /64. -rt |
|
| Back to top |
|
| |