Replies to This Discussion

Permalink Reply by Karl Auer on August 6, 2010 at 1:34am

Kevin and I have been discussing this, and thought we might float a few ideas here, to see what people thought would be most useful in the DNS department. Let me expand on what Kevin said.

One thing we *can't* do is put a name into the customer's own DNS, because we don't have access to it! What we *can* do is provide a name in a suitable domain, say "sites.instant6.com", so that even without putting name in your own DNS, you can still reach your Instant6 site without having to type in the IPv6 address. We could either generate the name or allow the customer to specify one when they set up their account.

For people with no IPv6 capability at all, we could accept delegation of the customer domain to one of our IPv6-only nameservers; then we *could* put a name into the domain. IPv6 users would get information from our server about the name, IPv4 users would continue to get information about IPv4 addresses from the customer's own nameservers. However, that would mean that we would have total control of the domain as far as IPv6 entries were concerned, which is unlikely to be acceptable to many people anyway, and doesn't work for anyone that has other IPv6 DNS entries. And it's no easier to put an NS record into a domain than an AAAA record.

The reverse lookup is a bit easier; we could delegate the address to the customer's nominated nameservers, much as the tunnel broker does. Then the customer could have the forward and reverse entries under their own control - better "branding".

Anyway, let us know: What *should* we do about DNS and Instant6?

Regards, K.