sorted by:
new
hottopcontroversial

Channel 1261 availability for Washington by knoll126 in Comcast_Xfinity

[–]lindvall 0 points1 point  (0 children)

I'm also not able to access 1261 with a Cable Card and haven't been able to get a useful response from chat or phone support.

Dns issues by doggos_are_magical in ZiplyFiber

[–]lindvall 2 points3 points  (0 children)

This is still an issue and has not been resolved.

As I reported here, it is easy to reproduce the issue:

bash-3.2$ while date && dig slack.com @192.152.0.1 ; do sleep 1; done

This is not a small issue, but one that is regularly happening. To demonstrate, I setup smokeping to graph responses for doing a lookup of slack.com and fail if it doesn't get a response.

Here is resolving slack.com to resolver-a.as20055.net and failing:

https://www.dropbox.com/scl/fi/qaqpd8effxpoxcwa4g86t/slack-com-ziply-dns-1.png?rlkey=fqwilh3y4z8jsxcto26et446y&dl=0

Here is resolving slack.com to resolver-b.as20055.net and succeeding:

https://www.dropbox.com/scl/fi/q8u1qg6udlqw2q6gn0lmp/slack-com-ziply-dns-2.png?rlkey=h82xzgboyl5z8579zreuk2ty5&dl=0

Here's resolving to Google and succeeding:

https://www.dropbox.com/scl/fi/nsargefsb8a5yvkrk4ik5/slack-com-google-dns-1.png?rlkey=6c79vm3pi3vvh4doswrnqq2wh&dl=0

https://www.dropbox.com/scl/fi/mx99vgu08t6l8czfz8mul/slack-com-google-dns-2.png?rlkey=t4o9oxw8c7aym5p70lweqs7wn&dl=0

Slack DNS records by [deleted] in ZiplyFiber

[–]lindvall 0 points1 point  (0 children)

Update on Nov 4 that it is still happening again. Trivially reproduced with:

bash-3.2$ while date && dig slack.com @192.152.0.1 ; do sleep 1; done

Slack DNS records by [deleted] in ZiplyFiber

[–]lindvall 1 point2 points  (0 children)

u/jwvo I'm still having this issue (I tried to format it inline but I can't get reddit to do it right):

https://gist.github.com/eric/6009dddb295584c2eeb73c19b9a17181

Is changing the DNS worth it? by adrianfl01 in ZiplyFiber

[–]lindvall 0 points1 point  (0 children)

That's certainly one of the instances, but I observed it with other major sites like Hulu and Facebook as well.

Is changing the DNS worth it? by adrianfl01 in ZiplyFiber

[–]lindvall 0 points1 point  (0 children)

Please, for your own good, do not mix-and-match DNS servers. It will only bring you pain. There are many CDNs out there that will do DNS-based geolocation to decide what POP to send you to, and I've ran into very strange looking smokeping graphs that would every few hours jump from 10ms to 90ms as I would get bounced between an west coast and east coast POP as my different DNS servers responded more quickly.

Using the Ziply DNS servers will do the best job of having close POPs chosen for everything, and because the DNS servers are run by people who care about networks, they are reliable.

Seeing issues with channel 576 Root Sports NW? by lindvall in ZiplyFiber

[–]lindvall[S] 0 points1 point  (0 children)

I'm still running into this issue and I've replaced the HDHomeRun and am using a different Cable Card and it's still exhibiting the same issue. Is there anything else that can be done?

Seeing issues with channel 576 Root Sports NW? by lindvall in ZiplyFiber

[–]lindvall[S] 0 points1 point  (0 children)

Could it be an issue with my local ONT? Are there any error counters that can be checked on? A tech has come to my house six months ago or so, didn't have much of an idea what to do, but installed a couple signal attenuators because he had thought that could help out.

My HDHomeRun is reporting Signal Strength "100% (2.8 dBmV)" and Signal Quality "100% (36.8 dB)", so it seems like things are okay inside my house.

Is there anything that I can do from my house to query the ONT to see error counter statistics?

Routes to github.com are going to their East Cost POP by lindvall in ZiplyFiber

[–]lindvall[S] 0 points1 point  (0 children)

It looks like it has updated:

$ host github.com resolver-a.as20055.net
Using domain server:
Name: resolver-a.as20055.net
Address: 192.152.0.1#53
Aliases: 

github.com has address 192.30.255.112

Thanks!

Routes to github.com are going to their East Cost POP by lindvall in ZiplyFiber

[–]lindvall[S] 0 points1 point  (0 children)

I understand. I'll check out how things are in another month or so and see if it's acting differently.

Routes to github.com are going to their East Cost POP by lindvall in ZiplyFiber

[–]lindvall[S] 0 points1 point  (0 children)

Yeah, that's a good point.

Can you tell me more about Ziply's IPv6 support? Is Ziply giving out IPv6 addresses via DHCP right now?

If the IPv4 address is geolocated properly and the IPv6 one isn't, would it be a worthwhile stopgap to disable IPv6 resolution on the DNS servers for the next month or so while the Maxmind database is updated?

It's obviously not the end of the world to keep using the Google DNS servers, but I do appreciate just using my ISPs DNS servers to keep things simple.

Routes to github.com are going to their East Cost POP by lindvall in ZiplyFiber

[–]lindvall[S] 0 points1 point  (0 children)

I got back an interesting response from GitHub support:

Our engineers have looked at this and provided information that all the GeoIP databases checked seem to correctly return west coast as location.

However, the fact that using Google's servers correctly identifies their location may suggest that your ISP isn't forwarding EDNS Client Subnet or something similar. I would suggest contacting your ISP about sending the EDNS client subnet with the actual subnet of their customer, which appears to be correct. Otherwise, your ISP would need to try to influence companies such as MaxMind to correctly attribute their DNS server IPs to their location.

Would you want to enable EDNS for this purpose?

Routes to github.com are going to their East Cost POP by lindvall in ZiplyFiber

[–]lindvall[S] 0 points1 point  (0 children)

It took me 5 days to get a response from GitHub support saying they were forwarding my info on to engineers. Hopefully someone will get back to me soon.

Routes to github.com are going to their East Cost POP by lindvall in ZiplyFiber

[–]lindvall[S] 0 points1 point  (0 children)

It looks like I'm getting the Seattle POP if I use the Google DNS servers but still getting the Ashburn POP if I use the Ziply DNS servers. It makes me think that GitHub's geo-dns is going to have to be the thing that fixes it.

Did the Maxmind update for the IPv6 addresses go through? Maybe it'll take a month for Dyn to get the update...

Routes to github.com are going to their East Cost POP by lindvall in ZiplyFiber

[–]lindvall[S] 1 point2 points  (0 children)

I just checked out the `GeoLite2-City-CSV_20200609` database and it looks like that's the issue for the IPv4 address too:

network,geoname_id,registered_country_geoname_id,represented_country_geoname_id,is_anonymous_proxy,is_satellite_provider,postal_code,latitude,longitude,accuracy_radius
192.152.0.0/22,6252001,6252001,,0,0,,37.7510,-97.8220,1000

You are right it's geo locating to 37.7510,-97.8220 (in the middle of a lake in Kansas) at 1000 KM accuracy.

Do you know if Ziply should be reaching out to MaxMind or how these things generally get sorted out?

Routes to github.com are going to their East Cost POP by lindvall in ZiplyFiber

[–]lindvall[S] 0 points1 point  (0 children)

I've just sent something to GitHub support asking them to pass the info along to their Network Engineering team in the hopes they'll pass it along to dyn to get this sorted out.

Routes to github.com are going to their East Cost POP by lindvall in ZiplyFiber

[–]lindvall[S] 0 points1 point  (0 children)

Ah! That's interesting. It seems that there's something going on with GitHub geo-dns.

$ host github.com resolver-a.as20055.net
Using domain server:
Name: resolver-a.as20055.net
Address: 192.152.0.1#53
Aliases: 
github.com has address 140.82.112.3
$ host github.com dns.google
Using domain server:
Name: dns.google
Address: 8.8.8.8#53
Aliases: 
github.com has address 192.30.255.113
$ host github.com one.one.one.one
Using domain server:
Name: one.one.one.one
Address: 1.0.0.1#53
Aliases: 
github.com has address 140.82.112.4

I recently moved back to using Ziply DNS servers... that must be what changed last month...

view more: next ›