That pesky IPv6 😁

Mine spikes have now gone since the change to Quic DNS for IPv6.

When did Quic roll out IPv6 DNS servers? hopefully this will improve overall internet performance!

nbroad: ...I am however seeing some funny routing to Facebook, almost like it's flapping between NZ and AU.

 

... 

Maybe you suffer from the same as me?

=====

Joshua W.
Staff - 18/11/2024 2:21 PM

Hi ...,
While there was an ONT update last week we also preformed network maintenance, while we're not aware of any issues affecting IPv4 connectivity there is an ongoing issue with IPv6. It is possible that websites are timing out on IPv6 then switching across to IPv4 this would explain the behavior you're seeing. One way to find out is to disable IPv6 and see if it improves.

====

mentalinc: When did Quic roll out IPv6 DNS servers? hopefully this will improve overall internet performance!

They've had it for a few months now. I'm surprised that a BNG isn't handing them out (I was under the assumption all the BNG's were handing out the Quic IPv6 addresses). It was around the time they made their websites all available over IPv6.

ANglEAUT: Maybe you suffer from the same as me?

Nah that's different. It wouldn't make sense if Smokeping were doing that with an IPv4 test. But would be interesting if you fire up a thread on here, or in #troubleshooting on their discord because many of us, myself included, have rock solid IPv6 so sounds like you've got misconfiguration somewhere or have a hardware incompatibility.

The issue also appears to be resolved for me by manually setting Quic's DNS servers.

Thanks @michaelmurphy for highlighting to me that the DNS server being set by Quic IPv6 DHCP was a Quad9 server and then making my brain click that this would also affect IPv4 name resolution.

This is probably something Quic might like to fix up.  It appears I am being handed a single Quad9 IPv6 DNS server by BNG/DHCP and not Quic's servers.

Hi all,

As Facebook operated their own CDN, we can only help with one part of the puzzle, as all CDN providers have their own secret sauce for how and where they'd like to distribute traffic.

That being said, using our DNS servers will help, which are detailed on our support page as below:

Primary: 103.250.90.8 / 2407:8b00:f101:10::10
Secondary: 202.179.141.8 / 2407:8b00:f102:10::10

These should be getting automatically distributed down to you from your BNG, but have pinged someone on our side to make sure that is the case.

@ANglEAUT The issue you mentioned was a short-lived one, impacting only some customers, and was resolved early last week - unrelated to this.

nbroad:

 

Hi Quic and GZ,

 

I switched to Quic on Friday which was completely painless and all seems good so far.

 

I am however seeing some funny routing to Facebook, almost like it's flapping between NZ and AU.

 

Cheers.

 

So, to ask the obvious question why do you care if FB feeds out of NZ or AU? FB is not a time sensitive application and it seems a bit like extreme overthinking for an end user to monitor such a thing. If it was game servers I could understand but this seems unnecessary.

noroad:

 

So, to ask the obvious question why do you care if FB feeds out of NZ or AU? FB is not a time sensitive application and it seems a bit like extreme overthinking for an end user to monitor such a thing. If it was game servers I could understand but this seems unnecessary.

 

Because I'm a network and infrastructure engineer, a geek with OCD and I like things to be optimal?

Because this is how it's designed to work? If there's a local CDN then it's more optimal to keep traffic in country than to use a trans-tasman link?

🤓

quic:

 

These should be getting automatically distributed down to you from your BNG, but have pinged someone on our side to make sure that is the case.

 

yes this is/was the issue, QUIC IPv6 DHCP is handing me 2620:fe::fe which is dns.quad9.net

nbroad:

 

quic:

 

These should be getting automatically distributed down to you from your BNG, but have pinged someone on our side to make sure that is the case.

 

 

 

 

yes this is/was the issue, QUIC IPv6 DHCP is handing me 2620:fe::fe which is dns.quad9.net

 

Can confirm this is happening on my Quic connection also. BNG1-AKL1.

michaelmurfy:

 

mentalinc: When did Quic roll out IPv6 DNS servers? hopefully this will improve overall internet performance!

 

I run pi-hole so needed to change the config there to align with Quic DNS

nbroad:

 

Because I'm a network and infrastructure engineer, a geek with OCD and I like things to be optimal?

 

Because this is how it's designed to work? If there's a local CDN then it's more optimal to keep traffic in country than to use a trans-tasman link?

 

🤓

 

That's a fair answer. 

As someone who has built several ISP's I can tell you that CDN's do what they want when they want and ISP's have limited control over things.

@quic: ...

 

That being said, using our DNS servers will help, which are detailed on our support page as below:

 

Primary: 103.250.90.8 / 2407:8b00:f101:10::10
Secondary: 202.179.141.8 / 2407:8b00:f102:10::10

 

... 

My automatic IPv6 configuration begs to differ.

My Edgerouter receives cloudflare and quad9 also. Always has, I usually disable the DNS for IPv6, just reenabled it to check and no different.

Does it on both DHCP and PPPoE (which it currently is configured on)

ubnt@ubnt:~$ show dns forwarding nameservers
-----------------------------------------------
   Nameservers configured for DNS forwarding
-----------------------------------------------
103.250.90.8 available via 'dhcp eth0'
202.179.141.8 available via 'dhcp eth0'
2620:fe::fe available via 'system'

Chorus BNG1-AKL1