Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 15 submissions in the queue.
Meta

soylentnews.org experiencing DNSSEC issues

posted by NCommander on Monday October 09 2017, @12:04PM   Printer-friendly
from the always-something-new dept.

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
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 0) by Anonymous Coward on Monday October 09 2017, @01:18PM (1 child)

    by Anonymous Coward on Monday October 09 2017, @01:18PM (#579258)

    netstat, tcpdump, wireshark, etc...

  • (Score: 0) by Anonymous Coward on Monday October 09 2017, @01:41PM

    by Anonymous Coward on Monday October 09 2017, @01:41PM (#579264)

    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.