SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
SoylentNews
We've discovered over the weekend that soylentnews.org was failing to resolve with some DNSSEC enabled resolvers. After debugging and manually checking our setup, the problem appears to be occurring due to an issue with the Linode DNS servers when accessed over IPv6. As such, some users may experience slow waiting times due to these DNS issues. I have filed a ticket with Linode about this, and will keep you guys up to date.
73 de NCommander
This discussion has been archived.
No new comments can be posted.
soylentnews.org experiencing DNSSEC issues
|
Log In/Create an Account
| Top
| 15 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
The last time I saw him he was walking down Lover's Lane holding his own hand.
-- Fred Allen
(Score: 0) by Anonymous Coward on Monday October 09 2017, @12:35PM (8 children)
I suspect I'm connecting over IPv4 because I don't see any delays. However reading this I got the question how I would find out (other than wasting the time of the local sysadmins :-)).
Anyway, thanks for the information.
(Score: 0) by Anonymous Coward on Monday October 09 2017, @01:18PM (1 child)
netstat, tcpdump, wireshark, etc...
(Score: 0) by Anonymous Coward on Monday October 09 2017, @01:41PM
If I understand correctly, I'd have to run netstat at the very exact point when the browser makes the connection; something that should not be easy to do.
Sure, I could bring my own device and run tcpdump/wireshark on that; but I'm not sure the admins would like that ;-)
Hmmm … thinking about it, one way would be to run the browser under ptrace and sift through the system calls; however I'd hope there's a simpler way.
(Score: 0) by Anonymous Coward on Monday October 09 2017, @01:40PM (3 children)
If you're connecting to the site over Tor, it's over IPv4.
At least for now, Tor is IPv4-only. (Though I don't know the reason for that.)
Wireshark is probably your best bet to sniff traffic specifically to/from soylentnews.org to know for sure.
(Score: 0) by Anonymous Coward on Monday October 09 2017, @02:03PM (2 children)
Sites such as http://whatsmyip.net/ [whatsmyip.net] , https://whatsmyip.com/ [whatsmyip.com] , http://whatismyipaddress.com/ [whatismyipaddress.com] will tell the IP address you're connecting from. Using tor, I've seen some exit nodes on IPv6.
(Score: 2) by isostatic on Monday October 09 2017, @04:39PM (1 child)
I use https://ipinfo.io/, [ipinfo.io] which is fairly lightweight as a webpage, and is curlable from the commandline as a JSON output.
(Score: 1, Informative) by Anonymous Coward on Monday October 09 2017, @07:34PM
That only shows my legacy IPv4 address and not my real one.
(Score: 1, Informative) by Anonymous Coward on Monday October 09 2017, @02:51PM
The answers you're getting are wrong. Well, I guess they're answering your question, but your question is wrong.
The question isn't how you are connecting to the site; the question is how the DNS resolver you're using connects to the Linode DNS servers. And it's not so easy to ascertain that.
(Score: 3, Informative) by NCommander on Monday October 09 2017, @05:28PM
It's the DNS servers that are having issues, not soylentnews.org. Due to the way DNS works, it depends how your local resolver is talking to nsX.linode.com.
Still always moving