Those of you who keep up with the latest tech news know that Verisign has decided all invalid domain requests should be redirected to its servers (e.g. http://dhoafhasdlvnay74w5ta4wgy5an5yqa4.com) to present advertising. This makes a lot of network troubleshooting more difficult for everyone, and is a blatant abuse of their position. I sent them this email, and maybe if they get a few thousand more, they'll get the hint.
Verisign
- Thread starter CTho9305
- Start date
her209
No Lifer
- Oct 11, 2000
- 56,336
- 11
- 0
I believe you, but where are you seeing this? IE (all I bothered to test with) is happily refering me to the MSN unknown domain page not a verisign one...
Bill
Bill
guyver01
Lifer
- Sep 25, 2000
- 22,135
- 5
- 61
Originally posted by: jliechty
You'd see it in a browser that actually displays proper and useful error messages.
Well, since IE can detect the situation and refer me to a page it kinda cuts into CTho9305's argument that all invalid domains go to Verisign and this is a troubleshooting issue. As long as I get a valid error code to test against....
Bill
Originally posted by: bsobel
Originally posted by: jliechty
You'd see it in a browser that actually displays proper and useful error messages.
Well, since IE can detect the situation and refer me to a page it kinda cuts into CTho9305's argument that all invalid domains go to Verisign and this is a troubleshooting issue. As long as I get a valid error code to test against....
Bill
only in IE. network tools will end up resolving invalid stuff to actual IPs. not good.
Microsoft worshippers will say anything, whether it makes more sense or less, as long as it makes a cheap shot at an open source project or advocate.
How (I'm trying to understand what IE is seeing that it can trigger off of that the network tools can't)
Verisign is open source? I'm just trying to better understand what they did and why the change didn't affect IE (if they generically did something you'd think it would affect IE also). I'm just torn on how bad this actually is. MS added this functionality (and people complained about it then) but you can argue (not saying I will, but you can) that it's an ease of use issue that helps novice users (of course with IE already doing it, the extra benefit of Verisign doing it also to catch non IE users is questionable).
Bill
p.s. jliechty, suppose we can keep this a discussion and not immediately start flaming everyone?
Ok, played some more, see what your seeing now (they are sending back some records for just about everything). Does look like a local dns configuration option/choice (e.g. the bind patch to disable it), but I wonder if many ISP's will. Curiously they don't seem to be currently dishing anything up on 80 right now (can't telnet or point a broswer at it even tho they are resolving just about anything). Is it still working for you right now, what do you get if you telnet to them and try just dong a get / ?
Bill
Bill
This was an good point from the article "Vixie said a lot of spam spoofs the "from" domain, and that many ISP-level spam filters check whether incoming e-mail is from a valid domain or not. Instead of generating errors, the spam filter checks are instead being rerouted to the Site Finder service, and therefore appear to originate from a legitimate domain. " So, CTho9305, consider me fully onboard and annoyed with Verisign also
Bill
Bill
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 23K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 19K
-
-
-
Intel processors crashing Unreal engine games (and others)- Started by BFG10K
- Replies: 2K
Facebook
Twitter