cancel
Showing results for 
Search instead for 
Did you mean: 

Since when did the Plusnet Forum become IPv6 enabled ?

Nibiru
Community Veteran
Posts: 5,622
Thanks: 376
Fixes: 7
Registered: ‎11-08-2007

Since when did the Plusnet Forum become IPv6 enabled ?

I was just updating my Plusnet forum profile information, and happened to notice in the "Private Statistics" section that the "IP Address of Last Visit" was showing the IPv6 address of my computer, which therefore indicates that the Plusnet forum can now be accessed by either IPv4 or IPv6.

Using Firefox extension "SixOrNot" to indicate how the browser is connecting to each element of a web page, that shows that community.plus.net  is indeed now reachable using IPv6,  unfortunately the regular Plusnet website plus.net  is still IPv4 only.

I suppose this is a small and incredibly slow step in the right direction towards going IPv6  🙄

Plusnet FTTC 80/20 IPv4/30, Hurricane Electric 6in4 IPv6/48, Pulse8 landline & calls, SamKnows 600N
Vigor 130 modem, pfSense 2.4.5-p1 router, 5 WAPs, Devolo dLAN 500, Gigaset N300A-IP VoIP DECT
1 REPLY 1
MJN
Pro
Posts: 1,226
Thanks: 112
Fixes: 4
Registered: ‎26-08-2010

Re: Since when did the Plusnet Forum become IPv6 enabled ?

Good spot! I just hit the Like button! Then unhit it.... 😞

 

The reason the forums are reachable over IPv6 is because they're fronted by Amazon's Cloudfront CDN:

 

; <<>> DiG 9.16.1-Ubuntu <<>> community.plus.net aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59263
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;community.plus.net. IN AAAA

;; ANSWER SECTION:
community.plus.net. 21086 IN CNAME aptgm87544.lithium.com.
aptgm87544.lithium.com. 899 IN CNAME d14xs8zr41zt1m.cloudfront.net.
d14xs8zr41zt1m.cloudfront.net. 59 IN AAAA 2600:9000:2133:1400:1d:4bc7:b280:93a1
d14xs8zr41zt1m.cloudfront.net. 59 IN AAAA 2600:9000:2133:9a00:1d:4bc7:b280:93a1
d14xs8zr41zt1m.cloudfront.net. 59 IN AAAA 2600:9000:2133:1200:1d:4bc7:b280:93a1
d14xs8zr41zt1m.cloudfront.net. 59 IN AAAA 2600:9000:2133:5a00:1d:4bc7:b280:93a1
d14xs8zr41zt1m.cloudfront.net. 59 IN AAAA 2600:9000:2133:6800:1d:4bc7:b280:93a1
d14xs8zr41zt1m.cloudfront.net. 59 IN AAAA 2600:9000:2133:c000:1d:4bc7:b280:93a1
d14xs8zr41zt1m.cloudfront.net. 59 IN AAAA 2600:9000:2133:fc00:1d:4bc7:b280:93a1
d14xs8zr41zt1m.cloudfront.net. 59 IN AAAA 2600:9000:2133:e600:1d:4bc7:b280:93a1

;; Query time: 36 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat Mar 13 13:54:15 GMT 2021
;; MSG SIZE rcvd: 347

 

whereas their website sits on their own infrastructure:

 

; <<>> DiG 9.16.1-Ubuntu <<>> www.plus.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35388
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.plus.net. IN A

;; ANSWER SECTION:
www.plus.net. 18725 IN CNAME portal.plus.net.
portal.plus.net. 16320 IN A 212.159.9.2
portal.plus.net. 16320 IN A 212.159.8.2

;; Query time: 16 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat Mar 13 13:57:57 GMT 2021
;; MSG SIZE rcvd: 94

 

So it's not really Plusnet per se catching up on the IPv6 front.. 😞

 

Cloudfront has been IPv6-enabled since 2016 but only new customers have IPv6 enabled by default. Anyone that was on it beforehand has to tick a box to get it running so perhaps that's what's happened here given it's not been spotted previously? Unless of course it was just hiding in plain sight!