Slashdot Mirror


VeriSign Responds To ICANN's SiteFinder Advisory

dmehus writes "VeriSign's Naming and Directory Services division has written to ICANN President and CEO Paul Twomey regarding the recent advisory concerning VeriSign's DNS wildcard redirection service. In the letter, VeriSign's Rusty Lewis says that they are open to independent and objective technical concerns expressed by various Internet bodies; they have formed their own "independent" panel of industry leading experts to produce its own, separate report; and they will not voluntarily suspend SiteFinder. It's a very terse response, and frankly, I'd have expected more from them. Slashdot readers are encouraged to visit ICANNWatch for in-depth, expert discussion on this and other issues."

35 of 464 comments (clear)

  1. The bottom line... by jdhutchins · · Score: 1, Insightful

    The bottom line is that Verisign's DNS behavior screws up lots of other systems. If I go to a domain registration site, and ask it "is this domain registered?", it will go see if there is an IP for that domain. Verisign's behavior screws this up, because now all .com and .net domains will return an IP address.

    And it's being very disrespectful to the computer industry. Verisign is no better than Microsoft here; they are snubbing their noses at what they agreed on. They need more than just a slap on the wrist. They need to learn that they DO NOT have the right to do whatever they decided. Microsoft does it, but it doesn't mean that they can do it.

  2. So who actually expected them to cooperate? by samj · · Score: 2, Insightful

    Obviously this project has a significant return - otherwise they would not have invested some amount of time and energy into its implementation, knowing the backlash that was to be expected. That said, you really thought they'd give it up without a fight, especially considering the damage they've already done to their brand? Oh the arrogance.

  3. Another real danger is... by Atario · · Score: 4, Insightful

    ...that enough of a ruckus will be kicked up over this that someone will have the following bright idea:

    Let's make this illegal!

    Voila. Government steps in to take over .net, .com., and .org. Everyone's screwed. So much for the free, cooperative, works-of-our-own-free-will Internet. Thanks, Verisign.

    --
    "A great democracy must be progressive or it will soon cease to be a great democracy." --Theodore Roosevelt
    1. Re:Another real danger is... by asscroft · · Score: 2, Insightful

      Good Points. It seems whenever the government gives a monopoly to a company, we get screwed. Also, whenever the government takes over a free market we get screwed.

      So, government monopolies are cool, but private ones suck. It's simple to understand. The government operates a monopoly with the mind set of doing this as cheaply as possible, while still being worth doing.
      Private corporations operate with the mindset of doing this to make as much profit as possible.
      There is a significant difference - especially if there is no other guy to compete with.
      In a market, while trying to achieve profits, you're also trying to gain and keep customers. But, once a government who was running a monopoly with the mindset of do this as cheaply as possible gives it's monopoly to a company, they get to run it as "make as much money as possible" and because there isn't any competition, they don't have to worry about keeping customers or playing fair or any of the things competition brings to make a free market the thing we all love so much about capitalism.

      In short, it's the WORST of BOTH worlds. They do it cheaply, the charge a lot, and they make business decisions without any regard to thier customer base, in order to maximize profits in an un-natural manner.

      In this case, since we can't break up the monopoly, the government of the people needs to take back control of these TLDs. Verisign needs to be FIRED.

      --
      because I have been enjoined by this Holy Office to abandon the false opinion which maintains that the Sun is the centre
  4. NULL ROUTE by CEO+Guy · · Score: 2, Insightful

    I just null routed their ENTIRE array of IP addresses in my router. Now I can't even get to their site and accidentally buy a domain there. I also moved any domains I had with them to GoDaddy. if everyone else tells everyone they know to use another registrar or use another SSL key company they will see a loss :-) If ISP's null route them your defense is.. Well, you changed the rules why cant I?

  5. Re:Huh? by LostCluster · · Score: 2, Insightful
  6. Re:Huh? by Ark42 · · Score: 4, Insightful


    http://verisignsucks.museum/

    Just as an example.

    I think *.museum is ok to have a wildcard for though, since not everybody can go out registering a museum domain name. It works similar to .com.au (unless .com.au changed recently). .com/.net and any other domain that requires no special terms to register domains for, should NOT have wildcards.

  7. Re:Gimme a break by Jason1729 · · Score: 4, Insightful

    Why do you seek to portray Verisign as such a sleazy company?

    Because they are and always have been.

    Besides using the fact that they run the root servers to hijack all unused addresses, in the past they've sent misleading correspondance to domain name owners to get them to switch registrars to verisign when all they want to do is renew.

  8. Re:Huh? by rgmoore · · Score: 5, Insightful
    As to your call for us to suspend the service, I would respectfully suggest that it would be premature to decide on any course of action until we first have had an opportunity to collect and review the available data.
    That's an interesting thing for them to say, especially because earlier in the letter they said:
    All indications are that users, important members of the internet community we all serve, are benefiting from the improved web navigation offered by Site Finder.

    So which is it? Have they not yet had a chance to gather any data, or have they gathered the data and found that it's beneficial to users? Or, as seems most likely, are they just saying anything that they think will get ICANN off their backs for long enough for them to sell a bunch of registrations?

    --

    There's no point in questioning authority if you aren't going to listen to the answers.

  9. Is it accessible to the blind? by effer · · Score: 5, Insightful

    If not, what better target for a lawsuit!

  10. Re:Gimme a break by ADRA · · Score: 2, Insightful

    Well,

    Every single change they have EVER made to their DNS control realms have been sleazy, underhanded, or monopolistic.

    Domain Holding with the option for payments to free them up faster? They still do it. Hell just look at the slashdoty article history. The question should really be: What the hell have they done to improve the state of the internet? Their agenda's differ from those of us here because we want a free Internet and they want dollar signs.

    --
    Bye!
  11. Masterful piece of SCOspeak by jpetts · · Score: 2, Insightful

    In the footsteps of several other registries that have done the same, we recently deployed a wildcard in the .com and .net zones.

    You need to know what's going on to understand this bit. What they want people to think is that other registries are also deploying wildcards in the .com and .net zones, but in actuality what they are saying is "Other registries have deployed wildcards, and we are doing the same, but in the .com and .net domains".

    However, most people who are unhappy with VeriSlime will easily see through this piece of doublespeak.

    --
    Call me old fashioned, but I like a dump to be as memorable as it is devastating - Bender
  12. Re:Gimme a break by Frodrick · · Score: 3, Insightful
    Give them some credit; they are only trying to make a buck and survive as a company.

    Doing any sleazy thing one can imagine just because their lawyers think they can probably get away with it is not an appropriate way to do business - or an honorable one.

    And "just doing what they needed to do to survive" is the same excuse the Donner Party used.

  13. Re:Interesting by Elwood+P+Dowd · · Score: 2, Insightful

    If VeriSign were to be revoked their registrar status, ICANN would stand to lose millions.

    Right, but then they'd make someone else the registrar and get those millions from them.

    --

    There are no trails. There are no trees out here.
  14. Re:Interesting by Anonymous Coward · · Score: 1, Insightful

    It goes both ways: VeriSign needs ICANN approval in order to operate in the position it does. ICANN's in the superior position, in many ways, because there are plenty of other operators (read: hordes, foaming at the mouth) who'd kill to take over for VGNS.

    Now, the risk is great enough, for both parties, that I doubt either will push a hardline for long. VeriSign will back down at some later date, and ICANN won't seriously consider--for instance--yanking VGNS's right to operate.

    It's a cold war, MAD and all.

  15. .museum versus .com by TWX · · Score: 4, Insightful

    If one looks at the newsgroups as historically how something like this works, the .museum TLD is a highly restrictive, highly controlled domain. It's entire purpose is for respected institutions to be listed. So, them having a master index and a reply indicating an invalid domain makes sense, since the entire domain listing easily scrolls through a few screens only. It would be the equivalent of a comp or sci newsgroup; highly structured groups with moderation and content rules.

    .com is the tld equivalent of alt., where anyone can create and post anything, without moderation, without structure. Attempting to impose structure, in the form of sitefinder, is stupid in this instance, since the organizations represented in .com are usually for-profit or attempting to jockey for position. If I have a business, do I now have to register every possible combination of my domain to keep idiots from being redirected to a customer of mine because they paid verisign to add them to the referral page for a misspelling of my domain name? I also have to worry about verisign giving precedence to domains registered through them in the recommended sites, and if I have a godaddy.com-registered domain, will I end up being denied business that would normally have realised that they made a typo, to fix it and come to me?

    This is the real problem that I have with sitefinder. It being in the hands of a commercial organization who has exhibited a systematic behaviour of putting profit before anything else will only exploit this situation. They will start selling placement on messed up domain entries, they will start denying domains registered through other registrars the same regular placement as their own, and they will destroy what had been a fairly free and open system.

    I'd recommend that if Verisign doesn't immediately stop this insanity that we write to our legislators and demand that control of the TLDs that versign manages be removed and handed to ICANN to deal with directly.

    --
    Do not look into laser with remaining eye.
  16. Feeding the troll: my NSI experience by RobertB-DC · · Score: 2, Insightful

    I'm almost sad to see that the parent is currently modded 0, Flamebait. Someone has to play Devil's Advocate, even if it's to argue a patently ridiculous point.

    At the risk of feeding a troll, I'll point out a couple of things:

    AFAIK they have allways delivered a decent service at decent price to their customers. Compared to normal bussiness practise they are just very ethical in their behavior. As a long time customer I must say that they are nice to deal with compared to many of those unethical companies that you find on the internet that just want to scam you.

    An excellent analogy! Verisign is not as unethical as the companies that sell snake oil and redirect your phone call to Vanuatu. That's like saying I should be happy to just be beaten up in a robbery, 'cause I could have been killed outright. Thanks, I feel much better.

    My only dealing with NSI (in the pre-Verisign buyout days) was when they wouldn't transfer my domain to me from the original owner because of an obscure missing piece of paper (full story here). I got around the problem by transferring the domain to Domain Direct (affiliate link) and then to the much cheaper Gandi (no kickback), and I've never looked back.

    --
    Stressed? Me? Of course not. Stress is what a rubber band feels before it breaks, silly.
  17. Re:Interesting by burns210 · · Score: 2, Insightful

    correct me if i am wrong, but i though the US gov(or was it ICANN) gave verisign the registrat power over .com and .net...

    first, why can't we just take it back?
    second, why should so much power dealing with the interent be given to a corporation, why not a common non-profit organization handle the .com and .net(and .org, .tv, .info even.... excluding individual contries' domains)?

    The internet should be free, open, and very welcoming. domain registration should cost only enough to maintain the systems(the very POWERFUL systems) that handle that sort of thing... registrars shouldn't be in it for the money.

  18. Speaking of collecting data... by Anonymous Coward · · Score: 1, Insightful

    Someone correct me if I am wrong, but didn't their redirect site have some type of web bug as well as a cookie that doesn't expire for five years?

  19. herd this? by Anonymous Coward · · Score: 1, Insightful

    I remeber hearing this a while ago.

    "the road to hell is paved with good intentions."

    too far? we have arrived!

  20. alterNIC is dead 'cause the creator was a bad boy by Anonymous Coward · · Score: 2, Insightful

    however, openNIC is alive and well and kicking much ass. (or http://www.opennic.unrated.net for the unenlightened...)

  21. What you can do about SiteFinder by Jim+McCoy · · Score: 3, Insightful
    I will leave aside the hysterical responses others have proposed and suggest two simple actions that you can take to deal with this attempted coup by Verisign.
    • Contact your ISP (or do yourself if you run your own DNS) and be sure that they have implemented the update to BIND which locks out this behavior. The truly obsessives will also go out and start finding random DNS servers and testing them to see if they are allowing anything more than delegation from *.com and *.net and then notifying DNS admins as appropriate.
    • Make your feelings known to the other co-conspirator in this system: Overture. They are providing the back-end to this service and since they have been recently acquired by a publicly traded company (Yahoo) you may feel the need to contact Yahoo to express your opinion on this particular product line (or perhaps express your views in forums where Yahoo shareholders may be found.

    Hit them where it hurts, in the bottom-line. Complaining to everyone may get this fixed, but patching your nameserver and then going after the back-end may also get results.
  22. Re:Useful In Blocking Verisign? by Abcd1234 · · Score: 2, Insightful

    A better solution is to use something like dnsmasq, which is capable of blocking VeriSign's wildcard responses directly. This way, you'll get a proper NXDOMAIN response. This should be perfectly usable under MacOSX, since it's just a straight-up Unix daemon.

  23. Re:+4 Informative ? by signe · · Score: 3, Insightful

    Not really. You posted anonymously, I didn't. Nothing against you (since I have no idea who you are, obviously), but I set very little stock by anything posted without a name. I understand that there are reasons to post anonymously, such as to not bring down the wrath of an employer. However, there's still the concept of if you won't even sign your name to what you've said, how much can it be worth? Additionally, a lot of moderators take the tact of never moderating AC posts up. And you also started your post with a personal insult, which a lot of people automatically view as flamebait.

    Either way, the important thing is that someone got modded up to point out how wrong that guy was. And that he got modded down.

    -Todd

    --
    "The details of my life are quite inconsequential..."
  24. Re:I'm lost, please help. by ScottSpeaks! · · Score: 5, Insightful
    There are a variety of problems with this.
    • The most fundamental one from a systems-management standpoint (and the internet itself is one huge systems-management nightmare) is that DNS lookup is a core function that affects a lot more than just web browsing. You don't change such a core function without thoroughly testing the impact of such a change. At the very least, the co-operative nature of the internet requires that you at least tell everyone you're going to do it. And when people complain that you've just broken something, you damn well better put it back the way it was.
    • A case in point: A lot of anti-spam software uses DNS look-ups to identify bogus return addresses. Since DNS for .com and .net is no longer returning "not found" for bogus domains, this function is now failing.
    • Various legislatures and/or courts have passed/interpretted laws to forbid "squatters" from registering other people's trademarks (or typos of them) for themselves. Verisign has effectively just "registered" every unregistered/mistyped trademark and pointed it to their web site. For example, there's a local business who hasn't registered their name (a trademark) as a domain name. If someone asks for (thisbusinessname).com, Verisign will direct them to a web site (theirs) which instead suggests several other web sites. For the right price, a competitor of this business can have their web site listed here. This is no different from a competitor or unauthorised squatter registering the domain name... which they could be successfully sued for doing. The fact that Verisign is now profiting from the use of trademarks it does not own puts it on very shaky legal ground.
    • This is a classic case of abuse of monopoly power. In much the same way that (for example) the US FCC licenses broadcasters to use the public airwaves in ways consistent with the public good, Network Solutions (now owned by Verisign) was assigned responsibility for the .com and .net top-level-domains to be operated in ways consistent with the good of the internet community. Reckless management of that responsility, resulting in technical problems which it refuses to correct, and taking financial advantage of that trust in a way unavailable to any other entity... adds up to a "problem".
  25. Re:Huh? by generationxyu · · Score: 1, Insightful
    http://verisignsucks.tk
    http://verisignsucks.tv
    http://verisignsucks.dk

    This is a different thing, however. The .tk, .tv, and .dk TLDs are owned by specific countries (I can't remember exactly which). The specific subdomains are rented out for cheap, or free, along with banner ads, so the countries make revenue. Annoying, yes. Unethical, possibly. Against RFC... probably. But they own those TLDs, and can do whatever they want with them. Verisign does not own .com and .net. They are on contract from the US Federal Government to run the root nameservers for .com and .net.

    --
    I mod down pyramid schemes in sigs.
  26. I already suspended their service... by ErikTheRed · · Score: 2, Insightful

    ...at least on the DNS servers I control. Just redirect lookups on the .verisign.com (and .net and .org) domains to my local DNS servers which strangely enough don't seem to point the inquiries to verisign... Just had to clear it with Management first as a "privacy issue"...

    --

    Help save the critically endangered Blue Iguana
  27. Has anyone else noticed yet by paroneayea · · Score: 2, Insightful

    that the sitefinder "service" only returns domains by verisign customers? Kind of negates the defense that the sitefinder utility is helping people across the internet find what they really need.

    --
    http://mediagoblin.org/
  28. Letter to VeriSign by mikek2 · · Score: 2, Insightful

    [just fired this off to VeriSign]

    Dear VeriSign,

    Assuming for a minute that you had absolutely no idea that SiteFinder would break large portions of the Internet, I'm simply dumbfounded over your renegade attempt to hijack the Domain Name System.

    In all seriousness... what were you thinking?

    Did you intend to destroy your credibility, or was it merely an unintended side effect or your sheer arrogance?

    You've managed to rally the technical Internet community behind ICANN, the one organization which was a bigger laughingstock than you to begin with.

    Please, reconsider SiteFinder. The Bubble bust a long time ago.

    - a dissatisfied customer

  29. Re:Huh? by macdaddy · · Score: 2, Insightful

    It's even more interesting for them to come back with that when they themselves didn't do the very same data gathering and research before implementing the damned thing.

  30. Is Verisign in violation of federal law? by Anonymous Coward · · Score: 2, Insightful

    There seems to be an issue as to whether the Verisign SiteFinder "Service" violates federal law, namely, the Electronic Communications Privacy Act of 1986. I wish I could get links to work, but here are URLs that will give you the text of relevant sections of this law. Type the URLs carefully -- you wouldn't want them to be intercepted by Verisign.

    http://caselaw.lp.findlaw.com/casecode/uscodes/1 8/ parts/i/chapters/119/sections/section_2510.html

    and

    http://caselaw.lp.findlaw.com/casecode/uscodes/1 8/ parts/i/chapters/119/sections/section_2511.html

    A careful reading of these sections (18 U.S.C. 2510 and 2511) seems to suggest that Verisign's interception of mistyped URLs and emails, which could easily be argued to this casual observer to be both intentional and deliberate, might be a crime punishable by a fine and five years in prison. Sections of this law other than the ones cited above appear to indicate that statutory damages might be available to individuals who have had their communications intercepted.

    Someone with enough interest in the matter should contact a lawyer to get a more definitive answer.

  31. Re:Demand? Legislators? No: do something useful! by drakaan · · Score: 3, Insightful
    There was no problem...There are a number of unscrupulous registrars that also host tld's, and Verisign has recently proved itself to be the most sickeningly ballsy of them. If Verisign is allowed to generate revenue from a service that could never be competed against (and this specific one can't, without screwing things up worse than they already are), then why don't we just hand them the "keys to the internet" and walk away. Greed *is* foolishness, in this case as well as the one you pointed out.

    If selfless people existed, we might discuss what they could produce. That said, there are many generous people who are also intelligent and hard working that have made huge contributions to the computing world. As a result of them, we have the Internet, Web sites, Linux, and various less-well-known projects and products.

    I call bullshit on this one. Verisign is being greedy and abusing their stewardship. They don't own .com or .net, but they are making decisions for all of us that do own a part of it. If my $35.00 doesn't go to support those "willingly-provided" DNS servers, then why did I pay it? The solution is to roll back the clock 14 days and not have this "Service" implemented. If Verisign wants typos to drive traffic, they should do what everyone else is forced to do, and buy a browser.

    --
    "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
  32. Re:Huh? by Leto2 · · Score: 5, Insightful

    msaulters, for completeness, since you seem to be intimately knowledgeable on the RFCs, can you paste the relevant sections from these three RFCs that apply to Verisign's wildcarding?

    --
    <grub> Reading /. at -1 is like driving through Cracktown in a convertible that is stuck in 1st
  33. Re:Verisign's not the first to do this... by Abalamahalamatandra · · Score: 2, Insightful

    Okay, one more time...

    That's application level. You can shut it off. And if there comes a time when you can't, you're free to switch to a different browser, like, say, Opera.

    And it doesn't result in mistakenly passed spam checks, email address leaks to Veri$ign, and general screwed-upedness like a wildcard DNS does.

    Geez, does anybody get that "the web" is not a synonym for "the Internet" anymore?

  34. Re:Huh? by Olathe · · Score: 2, Insightful

    "Using what?"

    Probably router and nameserver configurations.