yea, delete and re-add scares me that the servers can't serve my domain during the time that it doesn't exist.

It doesn't really say you can email dnsadmin.  It just says that's who told you that you can't edit the record

I'd like to edit the SOA email address of one of my zones.  This doesn't seem possible in the current UI.

If I create a secondary zone, and convert it to a primary, then it's email address is whatever was imported, and doesn't change to "hostmaster.he.net", is this intended?

There doesn't seem to be any way to change the name/address of the master(s) associated with slave domains.  Is support for this possible?  (It's not urgent, but I wonder how I'll achieve it if I ever change my master's IP address)

This seems to be fixed now.

Cool, thanks!

Any update on this? My SmokePing graphs are showing the route is still down.  Should I email to create a ticket, or has a ticket been logged already (if so can you add me as a cc?)

Yea, I couldn't find a forum category for reporting network issues :-( Is there a better place/way?

$ mtr -w -c 2 -r --address 2001:470:1f08:ad6::2 gogonet.gogo6.com

HOST: darkflame                                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. normanr-1.tunnel.tserv5.lon1.ipv6.he.net  0.0%     2   46.9  46.2  45.5  46.9   1.0
  2. gige-g4-6.core1.lon1.he.net               0.0%     2   39.0  38.2  37.4  39.0   1.1
  3. 2001:7f8:4::1935:1                        0.0%     2   38.9  45.4  38.9  52.0   9.2
  4.                                       100.0     2    0.0   0.0   0.0   0.0   0.0

Traffic from SixXS to gogo6 is fine, so if traffic from tserv5 to google and kame.

Again, i turned off radvd, and unassigned all interfaces that previously had an Ipv6 address.
The question now, is how to I keep my tunnel IP from broadcasting?

To my knowledge on linux, if you shutdown radvd, then that stops all router advertisements.  If you shutdown radvd, and you're still getting auto-configuration happening on the network, then check for another copy of radvd running, either on the router (maybe it never got stopped for some reason), or on another machine on the network - you should be able to tell where the router adverts are coming from based on the 'default' route that gets set on the other machines.

Just to clarify, you should only have one copy of radvd running on the entire network, and it should be on the router only.

Obviuosly I'm missing something, but i don't know what it is.

You still have 2001:470:4:35::/64 routed to sixbone and eth0. You must delete the route to 2001:470:4:35::/64 via eth0

[6to4]

"prefix 2001:470:5:35::102/64" is invalid, so radvd should have refused to read it, you probably wanted "prefix 2001:470:5:35::/64".

Base6to4Interface is only for 6to4 addresses, which have to start with 2002:
All other addresses like 2001: are 6in4.  (There's also 6over4, but that requires IPv4 multicast)

Both, 2001:470:4:35::/64 and 2001:470:5:35::/64 route down your tunnel.  One is for use on the tunnel interface (The Tunnel Details page calls it the "Server/Client IPv6 address"), the other is for local network usage (The Tunnel Details page calls it "Routed /64").

If you use Base6to4Interface in ravd.conf, then you're forcing it to change the prefix to 2002:aabb:ccdd: (derived from the public IPv4 address, aaa.bbb.ccc.ddd on the interface supplied).  Based on your set up the only valid Base6to4Interface value MUST be eth0 (because that's your only public IPv4 interface).  Since you don't want to announce a 2002:: prefix, you actually want to totally remove the Base6to4Interface entry entirely!  If you don't remove Base6to4Interface, then the supplied prefix is ignored.

Looks like some confusion about what Base6to4Interface is used for: Base6to4Interface is only used for 2002::/48 addressing (aka 6to4), so you could have this:

Code:

        prefix ::/64
        {
                Base6to4Interface eth0;
        };

but only if you wanted to announce one of the /64's of your 2002:4658:b266::/48 range for an interface.  Basically the option reads the IPv4 address on the interface specified and uses it as part of the IPv6 address.  It doesn't look like you have sit0 configured so you don't have an active 6to4 configuration - so remove all Base6to4Interface entries from radvd's config file.

Your sixbone tunnel is referred to as a 6in4 tunnel, and he.net will assign two or three prefixes to it (/64 link, /64 allocation + optional /48 allocation)

The /64 link range should _only_ be assigned to the sixbone interface.  The /64 allocation can then be assigned to _one_ other interface of your choosing.  If you need to allocate to more interfaces than this you can split up your /48 and use that.  Notice that you can't have the same range assigned to more than once interface at a time.

So it looks like:
   link range: 2001:470:4:35::2/64
   allocated /64: 2001:470:5:35::/64 (this you don't have configured anywhere yet)
   allocated /48: 2001:470:d848::/48 (it looks like you assigned the entire /48 to eth1)

A minimal of what you want is something like:
   sixbone: 2001:470:4:35::2/64
   eth0: 2001:470:5:35::/64 (notice 4->5)
   eth1: 2001:470:d848::/64 (notice /48->/64)

An alternative is not to use your allocated /64 and configure something like:
   sixbone: 2001:470:4:35::2/64
   eth0: 2001:470:d848:1234:/64
   eth1: 2001:470:d848:5678:/64

because you've used two or your 65536 ranges from your /48 for eth0 and eth1, you can pick the '1234', and '5678' parts to be whatever four hexadecimal digits you want.

so an example radvd for those ideas would be:

Code:

interface eth0
{
        prefix 2001:470:5:35::/64
        {
        };
}
interface eth1
{
        prefix 2001:470:d848::/64
        {
        };
}

or

Code:

interface eth0
{
        prefix 2001:470:d848:1234:/64
        {
        };
}
interface eth1
{
        prefix 2001:470:d848:5678:/64
        {
        };
}

Obviously you need to update your routing tables to match too.

Hope that helps,

Cheers

It would be useful to add a Router to the Looking Glass page, that uses Teredo as it's default route.  That way people can check how 'far' it is to their ipv6 network from a Teredo host.  This might encourage them to run their own Teredo relay like miredo.