- IPv6 news and information

GeenStijl.nl is a Dutch blog founded in April 2003. Its trademark images are that of a female silhouette utilizing a chainsaw and that of a crown within a circle, both in a pinkish colour, although the crown in a circle is green with a black edge when it is embedded in online videos. In Dutch, the term “geen stijl” is used to describe an act by a person or organisation that lacks style.

GeenStijl often uses a provocative tone when referring to other internet sites and blogs. The blog attracts around 75,000 visitors each day, and counts as being one of the top 10 news sites of the Netherlands

After noticing yesterday that ‘geenstijl.nl’ also resolved to an IPv6 address, and not many hours later ‘www.geenstijl.nl’ also resolved to the same IPv6 address

$ host www.geenstijl.nl
www.geenstijl.nl has address 81.173.64.50
www.geenstijl.nl has IPv6 address 2a00:d00:ff:131:94:228:131:1

As far as i could tell the site is using a proxy to get the content from the IPv4 website using http://ipv6proxy.prolocation.net/ as a method of enabeling IPv6 connectivity.

According to the list on the http://ipv6proxy.prolocation.net/ There are several other related sites who now also have IPv6 connectivity:

www.geenstijl.nl
www.geenstijl.tv
geenstijl.nl
geenstijl.tv
www.spitsnieuws.nl
spitsnieuws.nl

Lets see this as an example that big sites can run dual stack without any problems.

Fahad AlSharawi is Managing Director of 2Connect in Bahrain and a member of the RIPE NCC Executive Board. In the latest video testimonial on IPv6 Act Now, he discusses some of the obstacles still faced in IPv6 deployment.

View more IPv6 testimonial videos, including discussions with Google, the Internet Society (ISOC) and Hurricane Electric.

Dear reader,

Worldwide, the number of Internet users is rapidly growing. For identifying and locating each user on the Internet,  IP addresses were developed. Currently, the expectation is however that in 2012 no more IP addresses are left to distribute which can seriously hinder the growth of the Internet.

A new protocol was developed as a solution to this problem: IPv6 protocol. Users can already implement IPv6 by replacing or modifying their software and hardware. A disadvantage is that IPv6 users are only able to communicate with other IPv6 users. At present, however, less than 1% of all internet users makes use of IPv6. Moreover, private companies are often unwilling to invest in IPv6.

This survey is designed as part of a research into the willingness to invest in IPv6 by companies. In this survey your opinion as IT professional will be asked regarding possible reasons that companies have for not investing in IPv6. If you are not familiar with the IPv6 protocol, you can read the remarks on the following page.

This survey will take approximately 5-10 minutes and is carried out by Delft University of Technology. The data and results will be treated completely anonymous.

Thank you in advance for your cooperation!

Satiesh Bajnath & Jos Vrancken
Delft University of Technology, Faculty of Technology, Policy and Management

http://spreadsheets.google.com/viewform?formkey=dGlVcHk4Slctc0FLRXA3bTc1NVhEZFE6MA..

Randy Bush, of Internet Initiative Japan Inc. (IIJ) in Japan, discusses IPv6 deployment. It includes practical information on the challenges, costs and planning of rolling out IPv6.

Have fun watching and stay tuned for more interviews from RIPE NCC!

The IPv6 Forum IPv6 Enabled Logo program objective is to accelerate deployment of IPv6. The goal of this program is to increase user confidence by demonstrating that IPv6 is available now and is ready to be used.

The IPv6 Enabled WWW Logo Program is the first one to be released. Its objective is to encourage adoption of IPv6 on the millions of web sites (WWW) at enterprises, Internet Service Providers (ISPs) and private users helping them to test and check their proper IPv6 readiness and adoption.

As you can see on the sidebar we from Fix6.net have recieved our Logo. And we are now “Officially IPv6 Enabled”

I found this bug a while ago when i noticed when i resolved using my IPv6 only recursor i didnt always get a result.

A few days ago i was tipped by Lannerd who showed me the following document explaining it:

https://finalx.nl/codex/IPv6-DNS

Read the document and you will understand why there are problems if you have an IPv6 only recursor.

Okay, the following document is mainly meant for providers that have to deal with authoritive nameservers. It pretends recursors (caching nameservers) never existed. Don’t be alarmed too much; if you have a recursor that serves your customers using IPv6 but in turn can resolve records over IPv4, you should be fine. If your recursor machine has no IPv4, you _are_ screwed.

As you might know, only 7 out of 13 root-servers have an IPv6 address. So when you can only reach those 7 theres a chance you get the wrong one by the nature of DNS.

japje@host:/$ dig +trace -6 -t ns fix6.net @internal.resolver

; < <>> DiG 9.5.1-P2 < <>> +trace -6 -t ns fix6.net @internal.resolver
;; global options: printcmd
. 93047 IN NS e.root-servers.net.
. 93047 IN NS h.root-servers.net.
. 93047 IN NS b.root-servers.net.
. 93047 IN NS m.root-servers.net.
. 93047 IN NS k.root-servers.net.
. 93047 IN NS l.root-servers.net.
. 93047 IN NS f.root-servers.net.
. 93047 IN NS j.root-servers.net.
. 93047 IN NS c.root-servers.net.
. 93047 IN NS g.root-servers.net.
. 93047 IN NS i.root-servers.net.
. 93047 IN NS d.root-servers.net.
. 93047 IN NS a.root-servers.net.
;; Received 500 bytes from #53(internal.resolver) in 3 ms

net. 172800 IN NS a.gtld-servers.net.
net. 172800 IN NS b.gtld-servers.net.
net. 172800 IN NS c.gtld-servers.net.
net. 172800 IN NS d.gtld-servers.net.
net. 172800 IN NS e.gtld-servers.net.
net. 172800 IN NS f.gtld-servers.net.
net. 172800 IN NS g.gtld-servers.net.
net. 172800 IN NS h.gtld-servers.net.
net. 172800 IN NS i.gtld-servers.net.
net. 172800 IN NS j.gtld-servers.net.
net. 172800 IN NS k.gtld-servers.net.
net. 172800 IN NS l.gtld-servers.net.
net. 172800 IN NS m.gtld-servers.net.
;; Received 511 bytes from 2001:7fd::1#53(k.root-servers.net) in 20 ms

fix6.net. 172800 IN NS ns1.tiscomhosting.nl.
fix6.net. 172800 IN NS ns2.tiscomhosting.nl.
fix6.net. 172800 IN NS ns3.tiscomhosting.nl.
;; Received 96 bytes from 2001:503:a83e::2:30#53(a.gtld-servers.net) in 283 ms

This result took me 21 tries.

There are 2 solutions for this problem:
1) Have all DNS root-servers listen on IPv6 and IPv4
2) Make sure the resolvers for your customers listen on IPv6, and have IPv4 connectivity themselves.

For an overview of current root-servers check http://www.root-servers.org/