Gigabit Berkeley

[mike.ely]

I just got gigabit internet from sonic and I'm very happy.

The only weird thing about it though is that there seems to be unreliability when it comes to Sonic's own DNS servers.

For example, when trying to access http://newwatch.slingbox.com, when using Sonic's own DNS servers, it wouldn't load.

I switched to cloudflare's 1.1.1.1 DNS server (based on a sonic customer service rep advice) and there's no problem loading it.

Is this something that will eventually be fixed?
I'm just a bit concerned about DNS issues not properly resolving domains.

Hi derekk,

From curiosity, are you seeing DNS issues not related to newwatch.slingbox.com or were your problems limited to just that host?

Did some digging using various DNS servers and depending on which server you query you will get a different result, which makes good sense as this host is being served by Akamai's excellent CDN - they'll want to return results that are most likely to be closest to your network location. Here's some example output, in this case from ns1.sonic.net:

Code: Select all

dig @208.201.224.11 newwatch.slingbox.com

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-10.P2.fc28 <<>> @208.201.224.11 newwatch.slingbox.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10468
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;newwatch.slingbox.com.         IN      A

;; ANSWER SECTION:
newwatch.slingbox.com.  300     IN      CNAME   newwatch.slingbox.com.edgesuite.net.
newwatch.slingbox.com.edgesuite.net. 16863 IN CNAME a402.b.akamai.net.
a402.b.akamai.net.      20      IN      A       184.25.56.114
a402.b.akamai.net.      20      IN      A       184.25.56.116

;; Query time: 7 msec
;; SERVER: 208.201.224.11#53(208.201.224.11)
;; WHEN: Mon Dec 10 10:14:02 PST 2018
;; MSG SIZE  rcvd: 159

Look at the two A records returned. Now here's the values returned when querying 1.1.1.1:

Code: Select all

402.b.akamai.net.      20      IN      A       96.17.109.154
a402.b.akamai.net.      20      IN      A       96.17.109.138

From 8.8.8.8:

Code: Select all

a402.b.akamai.net.      19      IN      A       184.25.56.116
a402.b.akamai.net.      19      IN      A       184.25.56.114

Or 9.9.9.9:

Code: Select all

a402.b.akamai.net.0.1.cn.akamaitech.net. 20 IN A 23.215.102.187
a402.b.akamai.net.0.1.cn.akamaitech.net. 20 IN A 23.215.102.176

Aside from the fact that our DNS server returned a good result for the site, the first thing that stands out to me is the really (really) low TTL value for the two A records returned: 20 seconds. More commonly you'll find these TTL values set to anywhere between five minutes to a couple hours. Again, this makes sense in the case of a high-traffic CDN, but what it means is that there's likely to be a great deal of churn happening behind the scenes especially given that you'll get different answers depending on where you're querying from.

I've looked in the logs on our DNS servers and didn't find any obvious issues. Can I request that you switch back to our DNS servers and see if your issue is repeatable? If it isn't, then the most likely cause was that there was an issue with whatever hosts our nameservers happened to be pointing at when you were experiencing the problem. If the issue is repeatable, then we really want to dig deep on it so please respond back.

[cmeisel]

For a while FDA’s went live every week and then, two blocks from me (fda39) it stopped. Any more movement ?

[derekk]

I just got gigabit internet from sonic and I'm very happy.

The only weird thing about it though is that there seems to be unreliability when it comes to Sonic's own DNS servers.

For example, when trying to access http://newwatch.slingbox.com, when using Sonic's own DNS servers, it wouldn't load.

I switched to cloudflare's 1.1.1.1 DNS server (based on a sonic customer service rep advice) and there's no problem loading it.

Is this something that will eventually be fixed?
I'm just a bit concerned about DNS issues not properly resolving domains.

Hi derekk,

From curiosity, are you seeing DNS issues not related to newwatch.slingbox.com or were your problems limited to just that host?

Did some digging using various DNS servers and depending on which server you query you will get a different result, which makes good sense as this host is being served by Akamai's excellent CDN - they'll want to return results that are most likely to be closest to your network location. Here's some example output, in this case from ns1.sonic.net:

Code: Select all

dig @208.201.224.11 newwatch.slingbox.com

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-10.P2.fc28 <<>> @208.201.224.11 newwatch.slingbox.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10468
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;newwatch.slingbox.com.         IN      A

;; ANSWER SECTION:
newwatch.slingbox.com.  300     IN      CNAME   newwatch.slingbox.com.edgesuite.net.
newwatch.slingbox.com.edgesuite.net. 16863 IN CNAME a402.b.akamai.net.
a402.b.akamai.net.      20      IN      A       184.25.56.114
a402.b.akamai.net.      20      IN      A       184.25.56.116

;; Query time: 7 msec
;; SERVER: 208.201.224.11#53(208.201.224.11)
;; WHEN: Mon Dec 10 10:14:02 PST 2018
;; MSG SIZE  rcvd: 159

Look at the two A records returned. Now here's the values returned when querying 1.1.1.1:

Code: Select all

402.b.akamai.net.      20      IN      A       96.17.109.154
a402.b.akamai.net.      20      IN      A       96.17.109.138

From 8.8.8.8:

Code: Select all

a402.b.akamai.net.      19      IN      A       184.25.56.116
a402.b.akamai.net.      19      IN      A       184.25.56.114

Or 9.9.9.9:

Code: Select all

a402.b.akamai.net.0.1.cn.akamaitech.net. 20 IN A 23.215.102.187
a402.b.akamai.net.0.1.cn.akamaitech.net. 20 IN A 23.215.102.176

Aside from the fact that our DNS server returned a good result for the site, the first thing that stands out to me is the really (really) low TTL value for the two A records returned: 20 seconds. More commonly you'll find these TTL values set to anywhere between five minutes to a couple hours. Again, this makes sense in the case of a high-traffic CDN, but what it means is that there's likely to be a great deal of churn happening behind the scenes especially given that you'll get different answers depending on where you're querying from.

I've looked in the logs on our DNS servers and didn't find any obvious issues. Can I request that you switch back to our DNS servers and see if your issue is repeatable? If it isn't, then the most likely cause was that there was an issue with whatever hosts our nameservers happened to be pointing at when you were experiencing the problem. If the issue is repeatable, then we really want to dig deep on it so please respond back.

For the time being, I've only experienced issues with that specific host, but then again, i have not been using other hosts other than the typical google.com, gmail, netflix, etc. hosts, so there may or may not be other issues with other hosts I have yet to visit.

I have switched to sonic's default DNS and the host is unable to load.
However, i just tried with cloudflare's dns and there doesn't seem to be any problems with 1.1.1.1

Also, I still have comcast service at my residence, and surprisingly, comcast is able to properly resolve the host without a hitch (made sure i'm not using 1.1.1.1 while on comcast).

[cmeisel]

http://newwatch.slingbox.com seems to be a problem for Sonic. I am still waiting for my Fiber but we have Sonic at work and it also can't resolve http://newwatch.slingbox.com but my verizon phone can, xfinity can.

[Clu42]

For a while FDA’s went live every week and then, two blocks from me (fda39) it stopped. Any more movement ?

All I know is that yesterday, I saw a couple of Sonic trucks installing Fiber near Berkeley Bowl, at Shattuck and Oregon. I see Sonic everywhere these days. Getting closer and closer to my house and Telegraph Avenue. I talked to one of the installers and said, "I can't wait to get rid of Comca$t." And he said lots of people are telling them that. Would make a great X-mas gift.

[derekk]

I just got gigabit internet from sonic and I'm very happy.

The only weird thing about it though is that there seems to be unreliability when it comes to Sonic's own DNS servers.

For example, when trying to access http://newwatch.slingbox.com, when using Sonic's own DNS servers, it wouldn't load.

I switched to cloudflare's 1.1.1.1 DNS server (based on a sonic customer service rep advice) and there's no problem loading it.

Is this something that will eventually be fixed?
I'm just a bit concerned about DNS issues not properly resolving domains.

Hi derekk,

From curiosity, are you seeing DNS issues not related to newwatch.slingbox.com or were your problems limited to just that host?

Did some digging using various DNS servers and depending on which server you query you will get a different result, which makes good sense as this host is being served by Akamai's excellent CDN - they'll want to return results that are most likely to be closest to your network location. Here's some example output, in this case from ns1.sonic.net:

Code: Select all

dig @208.201.224.11 newwatch.slingbox.com

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-10.P2.fc28 <<>> @208.201.224.11 newwatch.slingbox.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10468
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;newwatch.slingbox.com.         IN      A

;; ANSWER SECTION:
newwatch.slingbox.com.  300     IN      CNAME   newwatch.slingbox.com.edgesuite.net.
newwatch.slingbox.com.edgesuite.net. 16863 IN CNAME a402.b.akamai.net.
a402.b.akamai.net.      20      IN      A       184.25.56.114
a402.b.akamai.net.      20      IN      A       184.25.56.116

;; Query time: 7 msec
;; SERVER: 208.201.224.11#53(208.201.224.11)
;; WHEN: Mon Dec 10 10:14:02 PST 2018
;; MSG SIZE  rcvd: 159

Look at the two A records returned. Now here's the values returned when querying 1.1.1.1:

Code: Select all

402.b.akamai.net.      20      IN      A       96.17.109.154
a402.b.akamai.net.      20      IN      A       96.17.109.138

From 8.8.8.8:

Code: Select all

a402.b.akamai.net.      19      IN      A       184.25.56.116
a402.b.akamai.net.      19      IN      A       184.25.56.114

Or 9.9.9.9:

Code: Select all

a402.b.akamai.net.0.1.cn.akamaitech.net. 20 IN A 23.215.102.187
a402.b.akamai.net.0.1.cn.akamaitech.net. 20 IN A 23.215.102.176

Aside from the fact that our DNS server returned a good result for the site, the first thing that stands out to me is the really (really) low TTL value for the two A records returned: 20 seconds. More commonly you'll find these TTL values set to anywhere between five minutes to a couple hours. Again, this makes sense in the case of a high-traffic CDN, but what it means is that there's likely to be a great deal of churn happening behind the scenes especially given that you'll get different answers depending on where you're querying from.

I've looked in the logs on our DNS servers and didn't find any obvious issues. Can I request that you switch back to our DNS servers and see if your issue is repeatable? If it isn't, then the most likely cause was that there was an issue with whatever hosts our nameservers happened to be pointing at when you were experiencing the problem. If the issue is repeatable, then we really want to dig deep on it so please respond back.

Ok so the host is now loading, but when i actually watch the stream, it's SUPER slow. I just tried using comcast as my ISP, and the stream loaded without any problems whatsoever (consistent speed and no issues).

What's interesting is that yesterday, Sonic's own DNS was not resolving the host. And while I was using the 1.1.1.1 DNS, I had no problems with the stream and it was streaming at a decent speed. Today, Sonic's DNS did resolve the host, but the stream was REALLY slow, and now the issue is compounded that the 1.1.1.1 DNS is also slow while using sonic as my ISP, whereas with comcast, there's no issue in speed.

This is kind of worrisome as I need this specific stream to work without issues.

[derekk]

Host is now loading and there doesn't seem to be an issue while using Sonic's DNS. Weird

In any case, I hope this stays stable since I really love Sonic as a company!

[fvmany]

The Sonic crew is wiring up the poles on my block! I wonder how long it is between wiring poles and activating service?

Regardless, it appears that rollout of service is really picking up steam! Dane -- thank you for being so communicative here on the forum, as it definitely helped me keep faith that progress was being made.

[coyote2]

The Sonic crew is wiring up the poles on my block! I wonder how long it is between wiring poles and activating service?

Here's what Dane wrote back on Nov. 19:

"Once an FDA goes live, the drop crews come in and do all of the drops, sequentially down each street. It's really more practical than bouncing around the region all day. And each crew can accomplish 20+ per day, so it goes very quickly. As those complete, folks will see invitations to schedule their in-home installation. Don't worry, once the FDA goes live, it's a pretty quick process."

[cmeisel]

what area in berkeley ? just curious

The Sonic crew is wiring up the poles on my block! I wonder how long it is between wiring poles and activating service?

Regardless, it appears that rollout of service is really picking up steam! Dane -- thank you for being so communicative here on the forum, as it definitely helped me keep faith that progress was being made.