Home / Blogs

The Christmas Goat and IPv6 (Year 2)

Last year the municipality of Gavle asked my company if we could help them load share the streaming pictures of the famous Christmas goat in Gävle.

I accepted the invitation and set up a separate domain. My own interest in this was of course to track the usage of IPv6 and validation of DNSSEC from the visitors of the site. You can see the results from last year’s test here on CircleID.

Also for this year my company Interlan was involved in terms of load sharing. My special interest also stayed the same and the test this year was done in the exact same way, except for the fact that only one camera was used this year.

How did we do this? Below is a brief description:

At the time of the premier of the 2011 Christmas Goat, November 27, 2010, the following was set up: http://www.julbockmedipv6ochdnssec.se/kamera1 (no longer active)

In order to:

• Track native IPv6 with a RR with A and AAAA.

• Track those who can run IPv6 native or tunneled.

• Track validating DNS-resolvers with a domain that has a faulty DNSSEC.

From the above we were able find out that both usage of native IPv6 and DNSSEC validation have increased quite a lot this year. The native IPv6 users increased from 0.1% to 0.5% and the DNSSEC validation from 44% to 72%.

52% of all visitors were able to reach the http://[2001:b48:10:3::215]/ipv6.jpg where 74% running Teredo, 25% 6to4 and 1% native IPv6.

Unfortunately the Christmas Goat did not have the same luck as the one in 2010. By the morning of Friday, the 2nd of December, it was burned down.

The total time of the test this year was hereby limited to a short period. But with the experience from the test last year, and this year, I only need few days to get quite an accurate percentage of the use of IPv6 and DNSSEC from the visitors. This year I did a check after two days, last year I checked several times and the result was surprisingly correct after only a few days.

The operating systems used by visitors were also as expected: Windows 7, Mac OS X and different smartphones were up and Windows XP and Vista down.

Hopefully I will be back in 2012 with another update on the IPv6—DNSSEC usage via the Christmas Goat in Gavle!

For now, a Merry Christmas and a Happy New Year to you all!

By Torbjörn Eklöv, Senior Network Architect, DNSSEC/IPv6

Filed Under

Comments

Fun experiment Dan York  –  Dec 14, 2011 4:21 PM

Torbjörn,

Thanks for sharing the results again this year.  Purely out of curiosity, were you able to get any stats on which browsers were being used with regard to DNSSEC validation?

Thanks,
Dan

Browsers Torbjörn Eklöv  –  Dec 15, 2011 7:01 AM

Dan, I must do some cat, awk and grep in my logfiles to see if I can get any useful information.
I’ll give it a try and post the result here then. 

/Tobbe

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

VINTON CERF
Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Related

Topics

Domain Names

Sponsored byVerisign

Cybersecurity

Sponsored byVerisign

IPv4 Markets

Sponsored byIPv4.Global

New TLDs

Sponsored byRadix

Brand Protection

Sponsored byCSC

DNS

Sponsored byDNIB.com

Threat Intelligence

Sponsored byWhoisXML API