|
[Connectivity] Can anyone reach feedly.com on Comcast?Yesterday feedly.com had to change their IP address due to a DOS attack. I can get to feedly if I use my ATT wireless connection but if I am on Comcast, it just stalls from both my computer and smartphone. Comcast's DNS contact page just stalls out and will not complete so I cannot get a message to them to refresh their DNS servers.
Anyone else?
Thanks |
|
graysonf MVM join:1999-07-16 Fort Lauderdale, FL |
[Connectivity] Re: Can anyone reach feedly.com on Comcast?Works fine here using Comcast DNS servers. Maybe your DNS cache still has the old IP. Try clearing it. |
|
ARRIS SB6141 Cisco 2851 Asus RT-AC66
|
to Youngjm
no go here, it's going to take awhile (maybe 24 hours or more) for those old records to expire, they changed the DNS servers (from gandi to cloudflare) for feedly not JUST the A record (which would have been 5 minutes). And they are not accepting raw IP connections, so using IP won't help. Use nslookup -type=ns domainname.com to see DNS servers cached from dos/windows command line.
edit: I was using 75.75.75.75, which likely redirects to Midwest servers like yourself. Will have to use alt client DNS servers, like 8.8.8.8 Google. looks like Comcast Southeast has new records. |
|
NetFixerFrom My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU
|
to graysonf
said by graysonf:Works fine here using Comcast DNS servers. Maybe your DNS cache still has the old IP. Try clearing it. Hmm, not here: C:\>dig feedly.com @68.94.156.1
; <<>> DiG 9.9.2 <<>> feedly.com @68.94.156.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46094
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;feedly.com. IN A
;; ANSWER SECTION:
feedly.com. 243 IN A 108.162.200.248
feedly.com. 243 IN A 141.101.127.247
;; Query time: 62 msec
;; SERVER: 68.94.156.1#53(68.94.156.1)
;; WHEN: Thu Jun 12 07:56:23 2014
;; MSG SIZE rcvd: 71
C:\>dig feedly.com @75.75.75.75
; <<>> DiG 9.9.2 <<>> feedly.com @75.75.75.75
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30886
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;feedly.com. IN A
;; ANSWER SECTION:
feedly.com. 29 IN A 65.19.138.6
feedly.com. 29 IN A 65.19.138.5
;; Query time: 62 msec
;; SERVER: 75.75.75.75#53(75.75.75.75)
;; WHEN: Thu Jun 12 07:56:45 2014
;; MSG SIZE rcvd: 71
Ping results using Comcast DNS servers: C:\>ping feedly.com
Pinging feedly.com [65.19.138.6] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 65.19.138.6:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Ping results using AT&T DNS servers: C:\>ping feedly.com
Pinging feedly.com [141.101.127.247] with 32 bytes of data:
Reply from 141.101.127.247: bytes=32 time=17ms TTL=56
Reply from 141.101.127.247: bytes=32 time=19ms TTL=56
Reply from 141.101.127.247: bytes=32 time=19ms TTL=56
Reply from 141.101.127.247: bytes=32 time=19ms TTL=56
Ping statistics for 141.101.127.247:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 19ms, Average = 18ms
|
|
ARRIS SB6141 Cisco 2851 Asus RT-AC66
|
to Youngjm
Difference in Expire time for A vs NS records, is like 5 minutes vs 24-72 hours depending on how old record were setup
notice 300 (seconds) in first couple lines and over 96,000 in second section.
; > DiG 9.2.4 > feedly.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER- opcode: QUERY, status: NOERROR, id: 17530 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 4
;; QUESTION SECTION: ;feedly.com. IN A
;; ANSWER SECTION: feedly.com. 300 IN A 108.162.200.248 feedly.com. 300 IN A 141.101.127.247
;; AUTHORITY SECTION: feedly.com. 96919 IN NS sid.ns.cloudflare.com. feedly.com. 96919 IN NS anna.ns.cloudflare.com.
;; ADDITIONAL SECTION: sid.ns.cloudflare.com. 83534 IN A 173.245.59.143 sid.ns.cloudflare.com. 83534 IN AAAA 2400:cb00:2049:1::adf5:3b8f anna.ns.cloudflare.com. 14867 IN A 173.245.58.102 anna.ns.cloudflare.com. 101370 IN AAAA 2400:cb00:2049:1::adf5:3a66
;; Query time: 5 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Thu Jun 12 08:08:00 2014 ;; MSG SIZE rcvd: 199 |
|
graysonf MVM join:1999-07-16 Fort Lauderdale, FL |
to NetFixer
I get the same IPs on lookups and I can reach the web site fine. Must be some other problem. |
|
|
to Youngjm
comcast 75.75.75.75 returns 65.19.138.5 and 65.19.138.6.. the OLD addresses. |
|
|
DNS.comcast.com has a tool section to view the DNS cache. Most if the servers have not been updated. I switched to google DNS and feedly works. |
|
|
to Youngjm
Works fine on Comcast using OpenDNS.
Blob |
|
ropeguru Premium Member join:2001-01-25 Mechanicsville, VA |
to Youngjm
Using Comcast's DNS Cache Checker tool, all of their DNS servers are showing 65.19.138.5 & 6 as the IP, with the exception of Chicago and San Jose which show 108.162.200.248 and 141.101.127.247. » dns.comcast.net/index.ph ··· checheck |
|
graysonf MVM join:1999-07-16 Fort Lauderdale, FL |
to djlandkpl
Non authoritative DNS servers don't get "updated."
Records are cached until their TTLs expire. Then, if there is a request for a record from that server, the record is pulled from an authoritative for the domain DNS server and cached again. |
|
|
Youngjm
Member
2014-Jun-12 12:55 pm
I was finally able to reach the site but they are now under another attack. |
|
graysonf MVM join:1999-07-16 Fort Lauderdale, FL |
Changing the IP address isn't the answer to a DOS attack against a host name. |
|
noc007 join:2002-06-18 Cumming, GA |
to Youngjm
Looks like they may still under a DOS attack. This is on their blog:
Denial of service attack (part 2) Posted on June 12, 2014 by @feedly 7:26am PST: We are currently being targeted by a second DDoS attack and are working with our service providers to mitigate the issue.
As with yesterdays attack, your data is safe. We apologize for the inconvenience and will update this blog post as more information is available or the situation changes.
/Josh |
|
tshirt Premium Member join:2004-07-11 Snohomish, WA |
tshirt
Premium Member
2014-Jun-12 1:21 pm
Any clue as to WHY they are being DDoS'ed? (which tend to be more political then criminal attacks) did they do something BAD!!! (a relative term) |
|
camperjust visiting this planet Premium Member join:2010-03-21 Bethel, CT |
camper
Premium Member
2014-Jun-12 1:27 pm
  From their blog: "2:04am PST Criminals are attacking feedly with a distributed denial of service attack (DDoS). The attacker is trying to extort us money to make it stop. We refused to give in and are working with our network providers to mitigate the attack as best as we can...." |
|
tshirt Premium Member join:2004-07-11 Snohomish, WA |
tshirt
Premium Member
2014-Jun-12 2:07 pm
ahh yes the net mafia |
|