Follow Slashdot blog updates by subscribing to our blog RSS feed

 


Forgot your password?
Close
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

Check out Videos
×

Comment: Re:Great...now just one more issue.... (Score 1) 681

by adric (#34308474) Attached to: Making Airport Scanners Less Objectionable

Is somebody in Kansas City seriously going to consider a drive to Atlanta or Cleveland, or will they just stay home for Thanksgiving and decide that 15 minutes on Skype will have to be good enough?

I'm driving from Kansas City to Orlando in 2 days to visit family. My wife left a week earlier, making essentially the same trip by train.

So yes, there are definitely some of us who will opt for this approach.

Networking

Comcast Intercepts and Redirects Port 53 Traffic 527

Posted by kdawson
from the why-we-need-ipv6 dept.
An anonymous reader writes "An interesting (and profane) writeup of one frustrated user's discovery that Comcast is actually intercepting DNS requests bound for non-Comcast DNS servers and redirecting them to their own servers. I had obviously heard of the DNS hijacking for nonexistent domains, but I had no idea they'd actually prevent people from directly contacting their own DNS servers." If true, this is a pretty serious escalation in the Net Neutrality wars. Someone using Comcast, please replicate the simple experiment spelled out in the article and confirm or deny the truth of it. Also, it would be useful if someone using Comcast ran the ICSI Netalyzr and posted the resulting permalink in the comments.

Ya'll hear about the geometer who went to the beach to catch some rays and became a tangent ?

Close