Current status for IPv6 adoption in Denmark

The current state of IPv6 in Denmark is bad - not enough adopters and not enough work being done to secure that Denmark becomes ready for IPv6.

When IPv6 is ignored until it becomes a necessity it will become expensive to switch, while slowly moving to become IPv6 ready could have been done while expanding the infrastructure instead.

The purpose of this page is

  • to list some projects which use IPv6 in Denmark

You won't find a complete list of everything about IPv6 in Denmark - but please send an e-mail if you want to be included on this page. The current state is mainly about things that needs to be done about IPv6 in Denmark.

The page is written by Henrik Lund Kramshoej, hlk@kramse.dk and constitutes my opinion.

Current recommendation

Get connected to IPv6 using either

SixXs.net

or built-in support in operating system (Windows Vista contains some tunnelling, Mac OS X does similar with 6to4).

 

Transfer your DNS records to either your own server supporting AAAA (quad-A) records or service provider supporting it.

 

Start configuring services, and make sure you use them yourself. If you start using IPv6 in production, you are ready for other adopters.

 

Getting native IPv6

Sorry, but this is almost non-existent in Denmark.

There are a few ISP's which have gotten IPv6 addresses from RIPE. Most of those have only played around with IPv6 and do not see a business case for IPv6 - and thus they don't provide it to customers.

There have been some peering available at times, but current state is that unless you have good connections to an ISP which has IPv6 implemented already and know somebody quite well you will not be able to get native IPv6.

Tunnelbrokers

There are one tunnelbroker SiXXs which have a tunnelserver in Copenhagen Area, Denmark. If you are in Denmark and want to get connected with IPv6 your best bet is to use this tunnelserver through

SixXS

or 6to4. The SiXS tunnelbroker is managed quite well and the difference for packets that go through tunnels as opposed to using IPv4 are usually about 15-30ms when tested from this webserver to servers like www.kame.net.

 

 hlk@laura:hlk$ ping6 -c 5 www.kame.net 
PING6(56=40+8+8 bytes) 2001:16d8:dd00:19::2 --> 2001:200:0:8002:203:47ff:fea5:3085
16 bytes from 2001:200:0:8002:203:47ff:fea5:3085, icmp_seq=0 hlim=50 time=311.538 ms
16 bytes from 2001:200:0:8002:203:47ff:fea5:3085, icmp_seq=1 hlim=50 time=311.854 ms
16 bytes from 2001:200:0:8002:203:47ff:fea5:3085, icmp_seq=2 hlim=50 time=311.271 ms
16 bytes from 2001:200:0:8002:203:47ff:fea5:3085, icmp_seq=3 hlim=50 time=312.639 ms
16 bytes from 2001:200:0:8002:203:47ff:fea5:3085, icmp_seq=4 hlim=50 time=311.174 ms

--- www.kame.net ping6 statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 311.174/311.695/312.639/0.528 ms

hlk@laura:hlk$ ping -c 5 www.kame.net
PING www.kame.net (203.178.141.194): 56 data bytes
64 bytes from 203.178.141.194: icmp_seq=0 ttl=50 time=293.070 ms
64 bytes from 203.178.141.194: icmp_seq=1 ttl=50 time=282.781 ms
64 bytes from 203.178.141.194: icmp_seq=2 ttl=52 time=279.322 ms
64 bytes from 203.178.141.194: icmp_seq=3 ttl=50 time=282.756 ms
64 bytes from 203.178.141.194: icmp_seq=4 ttl=52 time=274.224 ms
--- www.kame.net ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 274.224/282.430/293.070/6.198 ms

The ping times may vary a lot across IPv6, but in general when compared to IPv4 the times are very similar, with IPv6 being only 10-15% slower. We will probably in a short timeframe also see IPv6 becoming faster in some setups.

Name service and IPv6

Make sure that you understand that name service and IPv6 are two things.

 

You are able to use ANY name server and serve Quad-A (AAAA) resource records even when the server only is connected to IPv4.

 

Since getting native IPv6 connectivity in Denmark is hard it is difficult to get name service through native IPv6.

 

Autoritative name server serving IPv6 records

Your current name service provider should be able to serve this just fine from any name.server.

 

If the interface they provide does not give you the ability to add Quad-A AAAA records consider moving to another provider.

 

Some companies serving AAAA records in Denmark are:

 

Tunnelled IPv6 connected autoritative name server

While not necessary to support dual-stacked hosts it will be neccessary for DNS servers to provide DNS across IPv6 in the future. Since the root DNS servers for some TLDs have IPv6 it is getting possible to run IPv6-only nodes, which can connect to the internet without any IPv4 address.

 

In Denmark we have few systems supporting IPv6 as dual-stacked and very few DNS servers which have AAAA records themselves.

 

So tell me about them ...

 

I know GratisDNS has AAAA records for some server, getting there

 

Native IPv6 connected autoritative name server

Current best bet is to get DNS hosting service or  a server outside DK.

 

I know DK-hostmaster are working to get connected with IPv6.

 

Native IPv6 connected recursive name server

Current best bet is to provide your own recursive name server on a dual-stacked host.