Slashdot Mirror


Network Solutions Changes WHOIS

Jeckle noted that NSI has massively revamped whois. Gone is the contact information, unless of course you use whois.networksolutions.com. (thanks to chrisd for pointing that out). The other servers only contain sketchy information. Less spam, but more control means I guess NSI was just kidding dropping that whole monopoly thing.

32 of 126 comments (clear)

  1. Whois proxies are your friend.. by mpk · · Score: 2

    I just alias whois="whois -h whois.geektools.com" and let the excellent Geektools whois proxy sort out which registrar. You can fling most any domain name at it, or an IP, and it'll work out the best place to get the data, then go and get it. Excellent stuff.

    Alternatively, visit http://www.geektools.com/whois.html to do the same thing.

    1. Re:Whois proxies are your friend.. by RLJ · · Score: 2

      Specifically:

      Geektools (a "public domain" project from CenterGate Research Group ) has:

      a) a whois proxy which proxies all known tlds, including gTLDs, ccTLDs. It is available as a command line proxy at whois.geektools.com. If you send a blank request, it will display a basic help screen.

      b) A web UI at GeekTools WHOIS

      c) Under the software link, a generic *nix source tarball if you want to run your own local proxy. GeekTools Software .

      d) Also under software, a windows binary that runs out of your system tray.

      They all operate in a similar way, except that the ui version will allow you to hotlink to elements of the answer (contact, nameservers, etc).

      Importantly, they know about .com .net. org. edu. .mil .gov and about 95 Country Codes automagically. It also knows about ip addresses, handles, arin records, radb policies, AS numbers, obfuscated ip addresses (spammers hack) etc.

      We try and keep on top of the new whois changes around the world. If anyone can fill holes for us in the list, please email us!

      We limit the number of queries per day to 50 from any ip address to thwart spammers. If you have a good legitimate reason for more queries a day, and give us your real contact information, we'll lift the restriction. Just email the address on the site.

  2. Guys, this is fine and desirable by Fastolfe · · Score: 5

    As part of the NSI's agreement with the ICANN (http://www.icann.org/ns i/nsi-registry-agreement-04nov99.htm), registry information like this is being split up.

    Instead of having everything lumped into one database, you have one centralized database (which this has turned into) containing only information about the domain itself and the responsible registrar that introduced it.

    If you want details about the domain, you then need to query the appropriate registrar's WHOIS server to retrieve it (this is why querying whois.networksolutions.com gets you the information you're used to getting). This is the most efficient way of handling information like this. Each registrar is responsible for keeping its own database of contact information and the "main" centralized database is responsible only for the domain and the registrar that set it up.

    Let's please THINK a bit about a topic and wonder if there might be a perfectly logical explanation for something instead of immediately insisting that someone is being evil and intends to destroy our lives or our Internet.

    A little bit of research won't kill you.

  3. which whois version does this? by Barbarian · · Score: 2

    I want to get it...whois with RedHat 6.0 doesn't.

  4. New Electronic Licensing = Better Than Shrinkwrap! by the+eric+conspiracy · · Score: 3

    The Data in Network Solutions' WHOIS database is provided by Network Solutions for information purposes, and to assist persons in obtaining information about or related to a domain name registration record.

    Network Solutions does not guarantee its accuracy. By submitting a WHOIS query, you agree that you will use this Data only for lawful purposes and that, under no circumstances will you use this Data to:

    (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via e-mail (spam); or (2) enable high volume, automated, electronic processes that apply to Network Solutions (or its systems). Network Solutions reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.


    WHAT AN EXTRA-ORDINARY CONCEPT

    I cannot believe that NSI is try to posit that anyone submitting a Whois query is in fact agreeing to the above contract, whose terms may be changed by NSI at any time! Man, I wish I had this kind of imagination. Just think - under the above they could change the terms and claim a retroactive charge of $1 per Whois query!

    Let's see if I can extend this to my own purposes.. hmmm

    The Information in this message is provided by the eric conspiracy inc. for the sole purpose of filling up the MySQL database running on servers owned by Andover Net. By accepting this posting into its database, Andover Net agrees to pay the poster 60% of all revenues associated with displaying this post on it's web pages, and supply the author a monthly accounting of such displays and associated revenue to enable accurate invoicing. Any other use including entertainment value, or attracting readers who may also be concurrently shown advertising for renumerative purpose is forbidden. By reading the text of any postings by the eric conspiracy inc., you agree to the terms of this license.

    This license may be changed at any time without notice. Changes to the license may include requirements for retroactive license fees associated with the posting, transferrence, display or reading of any data created by the eric conspiracy.

    Any transmission of this data over any electronic media whatsoever consitiutes agreement by the carrier to the terms of this license.

    No warranty as to the validity or fitness for use of this data is made. All implicit warrantees for fitness for use are disclaimed.



  5. This IS the end of the monopoly by turg · · Score: 4
    This is a great victory in ending NSI's monopoly. They constantly tried to confuse people into thinking that InterNIC and NSI were the same thing. Now InterNIC is properly represented as the database of domain names and NSI as the company that maintains the database under contract ("InterNIC" is a registered trademark of the US Dept. of Commerce)

    The whois server at internic.net will tell you which registrar serves that name, and the address of that registrar's whois server for more information.


    -
    <SIG>
    "I am not trying to prove that I am right... I am only trying to find out whether." -Bertolt Brecht

    --
    <sig>Guvf vf abg n frperg zrffntr
  6. Re:How to use the new system by Leto2 · · Score: 4

    > So we'll have to do this until we hack whois to support it:

    I heard about a very very handy whois server:
    geektools.com

    whois -h geektools.com dommain
    gives info on whatever domain, even if it's a countrycode TLD.

    (try whois -h geektools.com tudelft.nl)

    --
    <grub> Reading /. at -1 is like driving through Cracktown in a convertible that is stuck in 1st
  7. Re:This is just a symptom of the root problem... by Fastolfe · · Score: 2

    One-stop WHOIS. OK, this isn't a real big problem, but it would be nice to go back to a single repository for domain info. All domain info.

    Rest assured that this will appear in good time. Obviously it would be a huge boon to administrators to have such a tool, and it's pretty easy to code such a service that queries the central server and then queries the registrar, giving you all of the information available.

    which only gives me MORE spam, BAD service, MORE paperwork, MORE lawsuits, and invades my privacy.

    Maybe it's time you switched registrars then? The whole idea behind multiple registrars is so they can act competitively. Things like spam, bad service and excessive paperwork are detractors. People aren't going to want to do business with registrars like this, and will take their business to registrars that don't have these issues. It's simple economics. Contrast this with a government-subsidized monopoly over the system, where spam, bad service and excessive paperwork are the norm because they don't *have* to do any better. I wouldn't even have had a problem with them raising rates a bit if it meant fixes to these issues, but they were never under any obligation to do so, so it never happened. Competition in this area isn't necessarily a bad thing and will only lead to better and smarter ways for people to manage their domains.

    If you're truly concerned about your privacy, find a registrar that respects it. Do some investigating and find the registrar you want to do business with. If none exist, make it known that this is a major factor. Eventually someone will step up.

    ARIN assigns IP address blocks. It works (very well). If the "private" sector was so much better, why aren't we assigning IPs that way?

    The number of requests for IP's going through ARIN is a tiny fraction compared to domain names going through registrars. ARIN doesn't really assign IP's out to individual ISP's all over the world. More often than not, they will delegate large swaths of IP's to larger ISP's (or countries), who then sub-delegate to their own customers/ISP's.

    It works out to more of a top-level tree system, with ARIN delegating large chunks of IP space and letting those people delegate as necessary. The result is a minimal amount of work and overhead on ARIN's part, which makes their work inexpensive and perfect for a relatively small (even if government-sponsored) organization. Privatizing this wouldn't make much of a difference.

  8. Re:How to use the new system by Fastolfe · · Score: 2

    Unfortunately, whois.networksolutions.com will not contain information about domains registered through other competing registrars. Slashdot.org is registered with NSI, which is why it shows up there.

  9. One line shell whois replacement by Siva · · Score: 2

    bleh...you dont need perl for this, just a couple gnu utils:

    fwhois @`whois | grep "Whois Server:" | cut -f2 -d':' | tr -d \[:blank:\]`

    or

    whois -h `whois | grep "Whois Server:" | cut -f2 -d':' | tr -d \[:blank:\]`

    --Siva

    Keyboard not found.

    --

    Keyboard not found.
    Press F1 to continue.
  10. Re:US != .COM by Hobbex · · Score: 2


    The US government is already regulating this market without asking the rest of the world what they think, so the line between that and them controlling it is really hair thin.

    If the americans are so afraid of their national tld, they might as well have the non-national ones as far as I care.

    -
    We cannot reason ourselves out of our basic irrationality. All we can do is learn the art of being irrational in a reasonable way.

  11. Re:How to use the new system by Billy+Donahue · · Score: 2

    swhois.net is much better than geektools.

    it does contact handles, and IP netblocks,
    and auto-redirects the whois to the right
    registry for a one-click whois showing
    contact info..

    --
    -- The Funk, The Whole Funk, And Nothing But The Funk
  12. Better by tweek · · Score: 2

    At least the email addresses aren't available now and I like that considering all the domains I host. I just recently made a ton of changes that stopped my contact email from being printed but this is hella better.

    --
    "Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
    1. Re:Better by iCEBaLM · · Score: 2

      At least the email addresses aren't available now and I like that considering all the domains I host.

      I suppose it better for you, but perhaps someone needs to contact a domain holder, good luck...

      -- iCEBaLM

    2. Re:Better by tweek · · Score: 2

      See the above reply.

      --
      "Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
  13. How to use the new system by Danny+Rathjens · · Score: 5

    Doing a whois to rs.internic.net will no longer give
    you the info about a domain on Dec 1st. It will just
    tell you who that domain is registered with.

    So we'll have to do this until we hack whois to
    support it:

    alias whois 'whois \!*@`/usr/bin/whois \!*@whois.nsiregistry.net |grep Whois\ Server: |
    cut -f2- -d:`'

    note: This syntax is specific to fwhois which is what is on Redhat boxen
    by default(whois is a symlink to fwhois.)
    fwhois user@host instead of whois -h host user

    p.s. Is there any kind of group/mailing list that is somewhere
    between flux(user level) and nanog(backbone level). I guess I
    should look for some kind of ISP operator's list.

    Posted on NANOG:
    "Newell, Tom" wrote:
    >
    > An FYI of an operational nature.......
    >
    > --Tom
    > Director of gTLD Programs
    > NSI Registry
    >
    > ##########################################
    >
    > Redirecting Port 43 Whois
    >
    > The following change is being made to comply with the recently
    > negotiated and signed agreements between the U.S. Department of
    > Commerce, ICANN, and NSI.
    >
    > Effective December 1, 1999 Network Solutions will be redirecting
    > port 43 (rs.internic.net) Whois from the NSI Registrar Whois to
    > the NSI Registry Whois. The NSI Registry Whois can currently be
    > found at whois.nsiregistry.net. After this occurs, port 43 Whois
    > will show the following information: domain name, registrar, Whois
    > server, registrar referral URL and the names of the name servers
    > associated with the domain. To obtain registrant and domain name
    > contact information, users will need to refer to the Whois service
    > provided by the registrar for the domain name.
    >
    > Send questions or comments to whois@nsiregistry.net.
    --

    1. Re:How to use the new system by breser · · Score: 2
      No swhois.net is not much better.

      It trys to look up my contact handle on ARIN, when ARIN contact handles always end in -ARIN (duhh). In fact anything that looks like a contact handle it sends to ARIN.

      It adds a list of things of the links that are on the left hand side of their website to command line queries, which takes about 20 lines worth of crap on the top. Network Solutions disclaimer is bad enough.

      The only issue I see with geektool is that it doesn't get handles very well. But at least it can handle NSI's handles.

  14. Shared registry by Gilbert+Coville · · Score: 3

    This is the whois server that was formerly available only at whois.nsiregistry.net. For the past few months, I had always appended either -h whois.nisregistry.net (or @whois.nsiregistry.net depending on the flavor of whois) to my whois queries. I used the shared registry, because it would also give information on domains registered with the new registrars (register.com, joker, etc...).

    I'm glad to see that the "default" whois.internic.net has now been switched over.

    I doubt Network Solutions did this on their own without some pressure. Does anyone know what particular event caused this change?

  15. No, worse. by seebs · · Score: 3

    Sorry, but no. We *need* every domain to have real, live, active contact addresses and phone numbers. It's a responsibility and accountability thing, just like postmaster@example.com. (Not having a working postmaster@ is an RBL'able offense, in some cases.)

    The solution is to stop the spammers, not to hide contact information which is *NECESSARY* to keep the system running.

    --
    My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
    1. Re:No, worse. by tweek · · Score: 2

      I agree that we need the contact information but that information is still available but not via the quick and easy whois as stated in the original post. I don't mind people contacting me about my domains with serious issues at all. I DO mind the fact that I need to beware of the Microsoft cookie recipe that will erase my harddrive if I don't send the message to a hundred people or that I might be interested in this fantastic offer on finding long lost pets fgor only 19.95 ;)

      --
      "Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
  16. Note.. by drwiii · · Score: 3

    Also, be sure to also check out the newly updated, mostly NSI-less InterNIC Web Site.

  17. not just a matter of spam.. by Barbarian · · Score: 2

    As an example:

    In the past, there have been "fan" sites for movies, revealed to have domains registered to companies marketing the movies. If you can't look up who registered a domain, how can you tell?

    (There was a slashdot.org story on this a few months ago.)

  18. Facts? They're irrelevant... by Moonwick · · Score: 3

    Rob, you should probably watch the sarcasm here. The only 'real' power that NSI has over domains now is the fact they run the central repository, the one that actually keeps the root servers inline.

    No matter what registrar registers a name (even NSI), NSI gets just $6 out of them, and it's the registrar's responsibility to run the WHOIS server for the domains of their customers.

    Can you come up with a better way to make whois work with multiple servers without totally revamping the utility and breaking everything out ther? The way things are now, (rs.internic.net just telling what WHOIS server to query for more information) is a fine solution, and it does little to 'prop up' NSI's perceived monopoly status.

    No matter what, someone's got to be in charge, and since NSI has had the most experience running (or screwing) things, this is probably the best way for things to be.

    --
    Only on slashdot can a posting be rated "Score -1, Insightful".
  19. whois changed? by BlueLines · · Score: 2

    It definitely was different this morning, but seems to be back to normal now...no matter, i usewhodat instead. /shameless plug. Actually i've used this for a while, since i work for an ISP that seems to attract register.com customers (Not only did they mess up whois, but try getting a verisign cert for a company registered there...)

    --
    --BlueLines "The cost of living hasn't affected it's popularity." -anonymous
  20. fixed! by Barbarian · · Score: 2

    There were a few lines missing in the script.


    #!/usr/bin/perl
    # whois3 -- do a whois on the default server
    # then parse output to find the server of the
    # registrar that manages that name.
    # Re:solution (Score:1)
    # by hucke (matt@hucke.org) on Wednesday December 01, @01:07PM MDT (#68)
    # (User Info) http://www.graveyards.com/
    # fixed by Barbarian (conanford@hotmail.com)

    die ("Usage: $0 domainname\n") if ($#ARGV);

    $item = @ARGV[0];

    @results = `whois $item`;

    for $line(@results)
    {
    chomp($line);
    $line =~ s/^\s//g;
    if ($line =~ /^[[]/)
    {
    print "$line\n";
    } elsif ($line =~ m/(Domain Name|Registrar|Name Server): (.*)/) {
    print "$line\n";
    } elsif ($line =~ m/Whois Server: (.*)/) {
    $server=$1;
    print "$line\n";
    }
    }
    close(W);
    if ($server)
    {
    print "Server: $server\n";
    # system("whois $item\@$server"); ## for RIPE whois
    system("whois -h $server $item"); ## for other whois
    }

  21. simpler script by Barbarian · · Score: 2

    Here's one that doesn't hide anything from the user, and works for non .com, .net, .org, and .edu domains:#!/usr/bin/perl
    # whois3 -- do a whois on the default server
    # then parse output to find the server of the
    # registrar that manages that name.
    # Re:solution (Score:1)
    # by hucke (matt@hucke.org) on Wednesday December 01, @01:07PM MDT (#68)
    # (User Info) http://www.graveyards.com/
    # fixed by Barbarian (conanford@hotmail.com)
    # made compatiable with non-US TLD's and a bit more verbose
    # now prints full response

    die ("Usage: $0 domainname\n") if ($#ARGV);

    $item = @ARGV[0];

    @results = `whois-real $item`;

    for $line(@results)
    {
    chomp($line);
    $line =~ s/^\s//g;
    print "$line\n";
    if ($line =~ m/Whois Server: (.*)/) {
    $server=$1;
    }

    }
    close(W);
    if ($server)
    {
    print "Querying Server: $server\n";
    # system("whois-real $dom\@$server"); ## for RIPE whois
    system("whois-real -h $server $item"); ## for other whois
    }


  22. How will address verifiers cope? by jbuhler · · Score: 2

    I believe that some (USA) web and FTP sites which offer encryption software use reverse DNS + whois lookups to determine if a download request comes from a domain known to be in the U.S.A. I had trouble downloading such software until my ISP added "US" to the street address in its whois entry.

    Aside from the fact that NSI has just hosed these sites' authentication mechanisms until they fix their scripts, I wonder how these sites will determine whose registry to check for contact information in the future?

  23. This is MORE data, but less convenient for most by The+Dev · · Score: 3
    What has actually happened here is that all
    domains, even those registered by competing
    registrars are now visible in whois. if you use
    the -h option followed by the appropriate
    whois server you get the same details as before.


    Of course this should all be integrated into one
    whois lookup but it's a good step in the right
    direction.


    You can put away the guns now, no data has been
    hidden.

  24. Planned for some time by JBReynolds · · Score: 3
    This change is a consequence of NSI's agreements with the Dept. of Commerce and ICANN. NSI announced it more than two weeks ago.

    Whois on rs.internic.net is now "registry whois" (previously on whois.crsnic.net), which includes an entry for what server to use for "registrar whois", where one can find contact information. The change is part of the transition away from using "interNIC" (a US Government trademark) to refer to NSI's registrar business.

  25. This is just a symptom of the root problem... by trims · · Score: 5

    OK, I can't stand NSI. However, as another poster pointed out, this is indeed a proper action on NSI's part - the "basic" whois information is available on a central server, and you querry the responsible registrar company for the particulars.

    HOWEVER, this whole boondoggle is stupid in the extreme. Honestly, I don't know who got it in their thick skull that multiple registrar agencies was a good idea. It's HORRIBLE. The DNS/Registrar system is a fundamental infrastructure requirement for the Internet to work. And, unlike virtually all other infrastructure of the Internet, it's already easily and logically divided along national boundaries. That is, DNS is segmented so that it's easy to figure out which nation (should) control which TLD.

    I hope this whole multiple Registrar thing turns into a massive mess, and the gov't has to step in. Now, I know everyone here doesn't like gov't regulation and is much more libertarian, but here me out:

    The US should form a quasi-governmental, NON-PROFIT organization along the lines of the USPS. It should be required to be self-sustaining (ie costs = revenue), but a non-profit. Call this org the USDR (US Domain Registrar).

    OK, once the USDR is in place, guess what problems go away:

    • Trademark fights. yes, you might still get A & B squabbling over who owns the domain, but guess what - the USDR gets to publish and force people (legally) to adhere to a Trademark policy. Current registrar's policies aren't worth the paper their written on, and can change at a whim (or for a "favored" client). USDR's rules would be legislated, and guess how hard it is to change them?
    • One-stop WHOIS. OK, this isn't a real big problem, but it would be nice to go back to a single repository for domain info. All domain info.
    • Elimination of Paperwork. yes, it is hard to believe that I'm saying that a gov't org would actually reduce paperwork, but think: look at all the hassles you have to go through to move a domain between registrars, especially if the owner is changing.
    • Privacy. By having a USDR, they could legally restrict people from using the WHOIS info for SPAM, etc. And actively pursue people who do. (When was the last time a Registrar even though about actively protecting your privacy?) The USDR isn't going to be selling your info to marketing companies. It's not going to be sending you spam mail about new services its offering to inflate its stock price.

    And, who knows, with a USDR, we might even get somebody to actually ENFORCE the TLD partitioning the way it should be (no more companies in .org!) and maybe even stop people from domain hording (you own the .com, .net, AND .org for your company???) Of course, this is dependent on having the USDR set up properly, with public input.

    Honestly, I think there are certain things that the government can do FAR better than private industry. The DNS system is one of them. I'm tired of being exploited by the for-profit Registrar system, which only gives me MORE spam, BAD service, MORE paperwork, MORE lawsuits, and invades my privacy.

    I'd trade the current system for a single gov't registrar in a heartbeat. Even if they doubled the domain fees, and made me wait twice as long to register something. My privacy is worth it, and so is the ease-of-use and efficiencies of a central authority.

    For those who don't agree, think about this: ARIN assigns IP address blocks. It works (very well). If the "private" sector was so much better, why aren't we assigning IPs that way?

    -Erik

    --
    There are always four sides to every story: your side, their side, the truth, and what really happened.
  26. Less spam? by EisPick · · Score: 2

    I doubt it.

    This isn't about privacy, it's about commerce. I'm sure NSI will be very agressive about selling the contact names to bulk email and snail mail advertisers.