Command Information receives IPv6 Enabled WWW Logo!

This week Command Information received the IPv6 Forum’s IPv6 Enabled/Ready WWW Logo!  Check out our IPv6 homepage to see it on our site, or take a look at the Validated List here: http://www.ipv6forum.com/ipv6_enabled/approval_list.php

From the IPv6 Forum, the purpose of the program is to “accelerate deployment of IPv6…” and to “increase user confidence by demonstrating that IPv6 is available now and is ready to be used.”

More from Command Information…

When IPv6 only internet is broken

800px-ams-ixkroot-serversnetI 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.

[email protected]:/$ 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/

Verizon mandates IPv6 support for next-gen cell phones

verizon_logoVerizon has posted specs for any LTE device that will be permitted on its LTE network. IPv6 support is mandated. IPv4 is optional. That’s quite a statement, since IPv4 traffic currently dominates the Internet.

LTE, Long_Term_Evolution , will provide much more bandwidth than current 3G cellular system.

A few relevant quotes from Verizon’s spec:

The device shall support IPv6. The device may support IPv4. IPv6 and IPv4 support shall be per the 3GPP Release 8 Specifications (March 2009)”. (section 3.2.4.1)

and

The device shall be assigned an IPv6 address whenever it attaches to the LTE network. (section 3.2.4.2)

For more info check our source.

And the Verizon LTE specifications: https://www22.verizon.com/opendev/Forum/LTE_Document_Archives.aspx

Report from the first German IPv6 congress

The first German IPv6 congress took place on May 28th & 29th in Frankfurt and was hosted by heise Netze, iX, and DE-CIX. Over 200 attendees, great presentations and tutorials made this congress a great success. The program included firsthand reports relevant to practical issues instead of marketing blurbs or general declarations of intent.

The keynote was given by Daniel Karrenberg who is the Chief Scientist at the RIPE NCC and ISOC Chairman. He explained that the most important reason to implement IPv6 now is not to increase security and to add features but it is all about solving the problem of the lack of remaining IPv4 address space.

For more, see DE-CIX News.

Tired of explaining why we need IPv6?

Are you tired of explaining why we all need to implement IPv6?

I am, i found this really interesting video that explains what IPv6 is and why that the IPv4 model is broken.



What is IPv6?Animated Explanations

Ripe in a bad spot

RIPE NCC is not allocating IPv4 addresses in the pace that I was anticipating. This has an interesting effect on the number of IPv4 addresses RIPE will have in their pool when the IANA pool gets depleted. If they continue to allocate in this low pace they will push their future allocations to IANA later and later. Soon they might overtake the questionable honor of being the last RIR to request an allocation from IANA. As we have an odd number of blocks in the IANA pool, the last allocations from IANA will only be 1 x /8. This will lower their pool at IANA depletion date and will in turn make RIPE the first region to run out of IPv4 addresses.

Furthermore, RIPE continues to allocate space from the 188/8 block. This block is in the various pool and was expected by everybody to be used by RIPE after the IANA pool gets depleted. The effect of the fact that they allocate from 188/8 is that RIPE will get depleted even earlier.

Consider this example. You are going on a hike with 4 friends and everybody gets a candy bar before they leave. An all you can eat buffet will be served the second day. After that the hikers will not get any more food until they reach the goal, three days away. When would you eat your candy bar? RIPE is eating their right now (on day one).