Loading Profile...
Feedly broken with OpenDNS?
I started using OpenDNS last night (after reading about the DNS exploit in Feedly). Everything seemed fine until this morning Feedly would not loud, instead I got an OpenDNS error page. (which I think you can see here: http://guide.opendns.com/?url=www.fee...) I assumed that Feedly was down like the page said, but after several hours and having not seen anything about it on the blog or here, I decided to look into it. I reinstalled and that didn't help, finally I switched back to my ISP's DNS servers and that fixed it. I hope we can figure out what is wrong because I can't live without Feedly, but my ISP's DNS servers aren't patched.
Thanks for the awesome extension!
Thanks for the awesome extension!
I’m frustrated but hopeful
7
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from the company
-
OK. the new DNS server information have replicated across. OpenDNS is now resolving feedly.com correctly. We should be back into clear skies. Sorry again for the inconvenience and thank you for your patience!
The company and 1 other person say
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?omg... cant live without OpenDNS and also Feedly....
waiting for a solution ... soon
I’m frustrated
-
Inappropriate?Thanks for the heads up. Forwarded the issue to your ops team. Will keep you posted.
-
Inappropriate?I got the same at home:
$ wget www.feedly.com
--14:37:52-- http://www.feedly.com/
=> `index.html'
Resolving www.feedly.com... failed: Unknown host.
But at my university computer it works ok:
Wget:
orjan@sister ~ > wget www.feedly.com
--14:40:05-- http://www.feedly.com/
=> `index.html.1'
Connecting to www.feedly.com:80... connected!
HTTP request sent, awaiting response... 200 OK
Length: 4,705 [text/html]
0K .... 100% @ 4.49 MB/s
14:40:06 (4.49 MB/s) - `index.html.1' saved [4705/4705]
Dig
orjan@sister ~ > dig www.feedly.com
; <<>> DiG 8.3 <<>> www.feedly.com
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<->www.feedly.com, type = A, class = IN
;; ANSWER SECTION:
www.feedly.com. 5M IN A 88.191.18.64
;; AUTHORITY SECTION:
feedly.com. 5M IN NS ctd2.itimemarketing.net.
feedly.com. 5M IN NS ctd1.itimemarketing.net.
;; ADDITIONAL SECTION:
ctd1.itimemarketing.net. 1d7h27m39s IN A 74.54.158.71
ctd2.itimemarketing.net. 1d7h27m39s IN A 74.54.158.71
;; Total query time: 4196 msec
;; FROM: sister to SERVER: default -- 130.240.16.33
;; WHEN: Thu Jul 31 14:37:52 2008
;; MSG SIZE sent: 32 rcvd: 136
I’m sad
-
-
Inappropriate?it works for me know... i removed opendns yesterday, still it was not working.... now it works even when i updated my dns to opendns :)
I’m happy to see feedly back
-
-
Inappropriate?Still not working for me either. -
Inappropriate?I tried going directly to the IP, 88.191.18.64, but that seems to take me to some photographers website.
EDIT: This seems to be because feedly is sharing the IP
http://www.myipneighbors.com/
I’m sad that I'm still without feedly
-
Inappropriate?Update: We decided to transfer our registrar and DNS server to your main registrar (the one we currently had to use because we bought the domain from seems to have some broken parts). The turbulence might therefore continue until the domain transfer is complete (they mentioned 1 to 7 days). People have reported 2 work arounds so far: 1) if you use OpenDNS you can temporary switch back to the DNS of your internet provider, 2) if you are technically savy you can manually change you host file with 88.191.18.64 www.feedly.com
-
Inappropriate?Thank you, I had completely forgotten about the HOSTS file!
I’m glad I can use feedly again
-
Inappropriate?Update: July 31st: 11:21 am. Transfer completed. DNS server changed. The change should replicate in the next hour or and everything should be back to normal. Special thanks to DNS expert (@davidu) for reaching out!
1 person says
this solves the problem
-
Inappropriate?feedly went off again after an hour... but now works after adding the line in HOSTS file...
thanks edwin for the support :)
I’m happy
-
Inappropriate?OK. the new DNS server information have replicated across. OpenDNS is now resolving feedly.com correctly. We should be back into clear skies. Sorry again for the inconvenience and thank you for your patience!
The company and 1 other person say
this solves the problem
-
EMPLOYEE
