Local Loop

{ 8 } Comments

1. David | 7 June 2011 at 4:35 pm | Permalink

   How are you doing to do that?

   By blocking connections to port 80 on the IPv4 IP or by removing the IPv4 DNS entry?

2. Simeon Miteff | 7 June 2011 at 6:16 pm | Permalink

   Removing the IPv4 DNS entry. It has a low TTL.

3. Aragon | 9 June 2011 at 11:49 am | Permalink

   It’s still off. :P

4. Simeon Miteff | 9 June 2011 at 12:05 pm | Permalink

   Hi Aragon!

   This is exciting, getting an IPv6-only comment. I was kind of expecting no-one would be reading at all :-)

   I’ve added the A-records back, now just waiting for it to take effect.

   Thanks for visiting,
   Simeon.

5. Adrian | 10 June 2011 at 10:35 am | Permalink

   How would someone with only IPv6 access your site?

   $ dig aaaa localloop.co.za

   ; <> DiG 9.6.0-APPLE-P2 <> aaaa localloop.co.za
   ;; global options: +cmd
   ;; Got answer:
   ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1604
   ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

   ;; QUESTION SECTION:
   ;localloop.co.za. IN AAAA

   ;; ANSWER SECTION:
   localloop.co.za. 3600 IN AAAA 2001:43e8:10::42

   ;; AUTHORITY SECTION:
   localloop.co.za. 86400 IN NS ns1.everydns.net.
   localloop.co.za. 86400 IN NS ns4.everydns.net.
   localloop.co.za. 86400 IN NS ns3.everydns.net.
   localloop.co.za. 86400 IN NS ns2.everydns.net.

   ;; ADDITIONAL SECTION:
   ns1.everydns.net. 22408 IN A 208.76.61.100
   ns2.everydns.net. 22408 IN A 208.76.62.100
   ns3.everydns.net. 55160 IN A 208.76.63.100
   ns4.everydns.net. 46937 IN A 208.76.60.100

   ;; Query time: 267 msec
   ;; SERVER: 172.16.0.12#53(172.16.0.12)
   ;; WHEN: Fri Jun 10 08:35:37 2011
   ;; MSG SIZE rcvd: 209

6. Simeon Miteff | 10 June 2011 at 12:59 pm | Permalink

   Hi Adrian

   Thanks for visiting!

   The dig query you pasted does return an AAAA record, so thats how, or am I misunderstanding your question?

   Regards,
   Simeon.

7. Adrian | 10 June 2011 at 1:46 pm | Permalink

   The DNS servers rely on IPv4, which means an IPv6-only client wouldn’t be able to query that DNS server (unless they were using a DNS server with both IPv4 and IPv6… but thats not the point).

   My point is, even though you only have an AAAA record, you are still relying on IPv4 to serve your page. Is that correct?

8. Simeon Miteff | 10 June 2011 at 2:20 pm | Permalink

   Ah, I knew I was missing something in your question!

   Indeed, you are correct. The lack of IPv4 DNS means that you had to be dual-stacked to access the site, which is bad.

   Thank you for pointing it out, I’ll have to fix that :-)

{ 2 } Trackbacks

1. Local Loop : Actually, I’m not ready to turn off IPv4 | 10 June 2011 at 5:06 pm | Permalink

   [...] a comment to my previous post, Adrian pointed out that localloop.co.za’s DNS is not IPv6-ready, so I hereby officially eat my [...]

2. South African IPv6 Usage | froztbyte.getBlog() | 13 October 2011 at 1:32 pm | Permalink

   [...] the past while Simeon’s blog has had a few posts concerning IPv6, and this alongside a few other posts that I’ve come across essentially [...]

Post a Comment