Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
The Internet The Almighty Buck Your Rights Online

Verisign Plans to Revive SiteFinder Advertising 'Service' 370

kiddailey writes "Claiming that their own independent examination of their controversial redirection service has found 'no security or stability problems', and that 'Internet users consider the service a helpful tool to navigate the web', Verisign has announced that it will give a 30- to 60-day notice before resuming the SiteFinder 'feature' that it voluntarily shut-down a couple of weeks ago."
This discussion has been archived. No new comments can be posted.

Verisign Plans to Revive SiteFinder Advertising 'Service'

Comments Filter:
  • WWW != Internet (Score:5, Informative)

    by ericspinder ( 146776 ) * on Thursday October 16, 2003 @08:52AM (#7228679) Journal
    Repeat after me, the World Wide Web is not the entire Internet. Now many applications will resolve a screwed up domain name and try to make a connection to Verisign's site. Instead of getting a "unknown host" programs will get a "service not found" which is a very different error. Or at least that is how I see it, I am only moderately knowledgable about DNS issues.

    • oh yeah?? well, then why is it that when I click "Internet Explorer" I get taken to the world wide web? answer me that smartypants..
    • Re:WWW != Internet (Score:2, Interesting)

      by medina ( 446303 )
      Not to mention the lovely timeouts one has to wait for...

      Have they addressed the issues of postmasters who can no longer handle mail to non-existing domains locally? (they have to send the mail to Verisign first, then handle the bounce, rather than relying on DNS). "Tweaks" probably won't fix this.
    • Repeat after me, the World Wide Web is not the entire Internet. Now many applications will resolve a screwed up domain name and try to make a connection to Verisign's site.

      Just install (or bug your ISP to install) BIND 9.2.2p2 or above and add:

      zone "com" {
      type delegation-only;
      };
      zone "net" {
      type delegation-only;
      };

      I've resolved millions of queries since I put that in and have NO problems. Unless Verisign plans to implement their sitefinder "service" using another mechanism to get

  • by tcopeland ( 32225 ) * <(tom) (at) (thomasleecopeland.com)> on Thursday October 16, 2003 @08:57AM (#7228703) Homepage
    From the Verizon site article:

    "Prior to ICANN's October 3 directive to shut down the service, Site Finder had
    been used more than 48 million times by Internet users to get where they want to go online."

    "...has been used more than 48 million times...". Makes it sound like folks are eagerly flocking to the Verizon web site to 'use' this service. It's as if the highway administration shut down all lanes of I-95 and then celebrated the increased HOV usage.
    • What I don't like about this service is that the typos are now kept by your web browser.

      In the past if the page was not found your web browser would do something about it like not display anything or display a custom search page. In both cases you wouldn't be confronted with your typo next time you try typing the right address.

      This service should be provided by the web browser and not Verisign, since at least that way you have the option of customising the service you use. BTW I have found out that some c
      • SUNY albany uses wildcarding, but only on our private network for registration.

        example ... when they come to school they get a temporary IP address. The DNS the get ONLY resolves to one address and then gets re-directed to a real website from there so that they can register. After that the get a real IP and a real DNS server.

        That way, any homepage or any site will resolve to the registration page.

        So wildcarding *can* be useful.
      • BTW While I think about, can anyone give me an example of a valid use of the DNS wildcard - its not that I don't believe that its useful, its just I don't know enough to prove that it is.

        Here's a few:

        • Musadoma's (approved) use of wildcarding to provide an Index of the .musuem domain [index.museum]
        • Directing user homepages to a central web server cluster for ISPs that use things like "http://customer.isp.net" for their user's homepages (* IN A www.isp.net). I've also used this to provide a customer bandwidth graph
      • Another obvious problem with the "site finder" is that it has mostly no clue in what language a user uses and hence will probably pop up an english search page for example, regardless of what language the user has. Hardly something good.
      • lwell, except for the 4-year-old bug in mozilla (#9203, if you're counting -- direct links from /. not allowed, but: http://bugzilla.mozilla.org/show_bug.cgi?id=9203) which makes it save incorrect URLs anyway...
  • I can only hope that Verisign will upset enough of the wrong people that there will be a move to dethrone them from the .net and .com domains. We would do better to have a not for profit running the show. Here's hoping that Verisign continues to be the pompous greedy company that we all know them to be!
    • Didn't someone post a patch for bind that takes care of the Verisign problem? Dunno how it would have worked, but it would be really funny to watch Verisign slowly fall off the 'net as people apply the patch...
  • "Internet users consider the service a helpful tool to navigate the web."

    I'd guess that most Internet users, not being part of the Slashdot-loving geek crowd, aren't even aware of the service to begin with. More than likely, the poll asks a question like, "Would you, as an internet user, appreciate a service whereby a system locates the correct web site when you make a mistake?" I can see most people saying "yes" to that.

    • The average user is on dial-up and is not amused after waiting 30 seconds for an ad page. wasted bandwidth.
  • Let's write to ICANN, and ask them to lift Verislime's mandate because they **BREAK** the internet.

    NOW!

  • There is a fundamental issue of standards that Verisign is not getting. The whole point of standards is so that everything runs smoothly, especially systems that rely on many many interconnected entities, like the internet.

    Whenever someone blatantly blows off standards to line their pockets a little, it has serious implications for the continuity and integrity of the system.

    If Verisign would like to continue making money from the internet, they should play by the collective rules that allow fair access
    • Geez.. That sounds like someone else we know....

      Hmmm... now who can it be?

      Perhaps.....

      SATA^H^H^HMicrosoft!!?!?!?
  • .COM anymore. I cant afford to sue or anything, but I can refuse to make their "service".

    3 words to Verisign: Fuck it all.
    • The problem isn't only with Verisign, although they have certainly put the focus on the problem. Some other top level domains than .com and .net also return results for non-existing entries, including *.nu and *.museum.
      Others, like *.name and *.no use wildcards, but use extra logic to return a "not found" (nxdomain) when the second leel domain doesn't exist.

      It's time for ICANN to enforce the standards, both against Verisign and the others. Since Verisign is the TLD entity that has the largest impact, the
  • by wherley ( 42799 ) * on Thursday October 16, 2003 @09:01AM (#7228730)
    The ICANN Information page on Verisign's Wildcard Service" [icann.org] elicits comments from Members of the Internet community. Emails are to be copied to wildcard-comments@icann.org [mailto] A selection of comments is viewable here [icann.org].
    I'd suggest making your comments now.
    Regarding the Verisign survey...more information about it is in this article [cbronline.com]. Excerpts:
    The survey, a telephone poll of 1,000 internet users who could recall seeing Site Finder, was conducted by Markitecture and Harris Interactive and commissioned by VeriSign. It has a margin of error of plus or minus 5%

    On the opposing side, Tucows Inc, a domain name registrar that competes with VeriSign, said a poll of its resellers (generally ISPs and web hosting companies) indicated that 90% of respondents wanted Site Finder turned off.
    • Although I'm on the side of the fence that opposes Verisign for all the obvious reasons, 99.9999% (you get my idea) of web users who mistype a domain name have no clue who Verisign is, why sitefinder is bad, and probably appreciate a clickable link for the domain they wanted. In other words, I do not believe such a survey is repetitive of "internet users."
  • Why not use a decentralized naming system based on public key crypto, and get rid of verisign and the rest of the leeches?
  • by Fnkmaster ( 89084 ) on Thursday October 16, 2003 @09:04AM (#7228747)
    I was under the impression ICANN essentially told Verisign this was not in compliance with their contract, and that it was unacceptable. When do we hear what the consequences are of continued, flagrant, and intentional violation of the public trust of .com and .net?


    Please, ICANN, you've always sucked before, but maybe there's hope for you yet. Enforce the terms of the contract with Verisign with extreme prejudice and terminate these scumballs.

    • Enforce the terms of the contract with Verisign with extreme prejudice and terminate these scumballs... with extreme prejudice.

      There we go, much better.

  • Legalities (Score:5, Insightful)

    by Doesn't_Comment_Code ( 692510 ) on Thursday October 16, 2003 @09:04AM (#7228749)
    Under 15 U.S.C. 1125d, cybersquatting is the illegal act of registering a domain intentionally to be confused with another. Thus, Ford could not register Chevrelet.com to themselves and hope people looking for Chevy's mistype and go to the Ford site.

    From what I understand, sitefinder is being used in almost the exact same way as the scenario I just mentioned. Verisign's activity is prohibited at least by the spirit, if not by the letter of the law.
    • I made a similar comment last time around -- IMO, the entire thing is aimed at discovering which "typo domains" are worth squatting on.

      Which is a Bad Thing to have in the hands of a supposedly-trusted domain registrar.

      If you don't think this is likely, try htobot.com -- this was originally registered as a joke, way backwhen hotbot.com was new, and it poked fun at your bad typing before sending you on your way to hotbot.com. NOW -- it's a portal site, evidently getting enough hits to be profitable.

      A relat
  • If Verisign tries to pull this crap again it just might be the excuse that ICANN needs to yank Verisign's contract.
  • by arcanumas ( 646807 ) on Thursday October 16, 2003 @09:05AM (#7228767) Homepage
    Their "team of experts" must consist of :
    1) a banker
    2) an enginee^H^H^H^H^H^H^H MSCE
    3) 3 Marketing droids
    4) the woman in the coffe shop across the road
    5) and ... Dalr McBride who can prove that the Internet contains data that belongs to SCO.

    They must have quite the dream team of experts to come to such a conclusion.

  • Is there anything ICANN can do about this? Can they revoke Verisign's right to the com's and net's? Or could they just make a "suggestion" to some governmental body?

    The Internet's the like Wild West and Verisign is setting itself up like a company town.
    • Since ICANN doesn't own the Internet, it can't tell domain registrars what they can or can't do. IMHO the only option is to sue them for using their monopoly-like power to their own advantage. If they want to do that, they should hook up with every search-engine, and search-related sites on the net, and argue that Verizon is driving them out of business.
      A case like this would not actually represent the spirit of the problem, but hey, the American legal system has seen things that are way more weird than thi
  • Service? (Score:3, Funny)

    by fetus ( 322414 ) on Thursday October 16, 2003 @09:08AM (#7228791)
    Oh those wonderful guys at VeriSign, giving us this 'service' free of charge! I mean, this is something I'd pay $30, even $60 a month to use!
    They've always been one of those 'for-a-better-internet' companies.
    God Bless Them
  • Comment removed (Score:5, Interesting)

    by account_deleted ( 4530225 ) on Thursday October 16, 2003 @09:09AM (#7228799)
    Comment removed based on user account deletion
    • Good idea. As was mentioned in the previous discussion, IBM and Google would be stable, trustworthy hosts. Now the question is -- would they be interested in doing the job?

  • Verisign!= Internet..

    I doubt their independent study as ICAAN's own independent study indicates otherwise and when Verisign was aske dto submit such facts it stalled
  • "We have consulted with out attorneys and they tell us we have a good chance of winning a legal battle with ICANN over this. As a side effect, we will rid ourselves of these pricks once and for all".

    This one has the potential for getting really ugly.

  • As a heavy but non-technical computer user it has been extremely frustrating for me to encounter 404 errors
    Is it me or 404 is for 'page not found'? And NOT DNS lookup error...
    • Is it me or 404 is for 'page not found'? And NOT DNS lookup error...

      Nope, it's not just you; a lot of articles are obviously being written by people for whom Internet == WWW, and this mistake is occuring a lot. The error they actually mean is NXDOMAIN, short for "Non-existant Domain", and not a "404" which is, of course, a HTTP error to indicate that the specific object was not found.

  • It's interesting that people seem to be missing the real fight. For probably a majority of desktop users (those using IE), they already have this "functionality" in the form of a redirect to search.msn.com [msn.com]. So it's kind of a fight of Verisign vs. Microsoft, not just Verisign vs. people who like good web standards.
    • by dougmc ( 70836 ) <dougmc+slashdot@frenzied.us> on Thursday October 16, 2003 @09:23AM (#7228983) Homepage
      For probably a majority of desktop users (those using IE), they already have this "functionality" in the form of a redirect to search.msn.com.
      Yes and no. Yes, to somebody using a browser, the two `services' seem pretty similar.

      However, there are some very important differences --

      The IE feature only affects web browsing. It doesn't break email, for example. Verisign's change does. This is by far the biggest issue.

      The IE feature probably doesn't remember `incorrect' URLs in the browser history

      The IE feature can be turned off, either in IE or by not using IE. To turn off Verisign, you need to patch your name server.

    • IE is not breaking any standards doing so. Redirecting failed DNS lookups on the _client_ side is actually a reasonable idea. Honestly, if Google had a good browser-plugin for Moz or IE that delivered a properly verbose "that site doesn't exist, here are some similarly spelled sites" I might use it.

      Verisign is fscking every client that would want to do this.
    • I am personally surprised that Microsoft has not been objecting to Site Finder. After all, if Verisign resolves everything in .com and .net, the redirect in Internet Explorer no longer works for these domains. This means less ad revenue for MSN.
      • Actually, MSN is showing an almost surprising amount of restraint, ad-wise; two links and a search box to MSN Search on the "error" page. And even the MSN Search is fairly ad-light, just one line text links at the bottom.

        I still find it a bit annoying, though, because if I made a simple typo (and the correct link doesn't showup in the 'did you mean?' list), then the URL in the address bar has been completely fscked, and I have to cut and or paste to get back to what I typed so I can correct it.
  • Verisign has announced that it will give a 30- to 60-day notice before resuming the SiteFinder 'feature' that it voluntarily shut-down a couple of weeks ago.

    Is 30 to 60 days long enough to de-authorize Verisign as a DNS registrar and find someone else to run those top-level domains?

  • "We have examined our service, and we think it works fine, and we think users love it."

    Well, duh. Did anyone actually expect something different? The ball is now firmly lodged in ICANN's court. They've done their legal blustering and letter writing - now they need to take it to court if Verisign continues flipping the bird to the Internet community.

  • Explain this verisign. An important site I use for business was doing fine, and even reregistered it's website domain recently, and yet when it expired, your bullshit service decided to post it's DNS as the proper place to go for that domain instantly. EVEN THOUGH THE SITE WAS ALREADY PAID FOR. Essentially you Highjacked their domain, and made it impossible for me to do business (over the internet) with them for 3 days straight.

    You claim there are no problems? HAH. There are so many holes and bugs in your
  • If I had the resources to survey users about SiteFinder-like services, here's what I'd ask:
    1. When you enter an incorrect domain, would you prefer a 404 error, or a web site with possible alternatives?
    2. If you answered "yes" to question 1, would you prefer for this service to appear all the time, or only when your incorrectly typed domain ends in ".net" or ".com"?
    3. If you answered "yes" to question 1, would you like to be able to set a preference in your browser that allows you to choose among alternative comp
    • This is the problem, and it's people like you.

      NXDOMAIN is not 404. Learn what a 404 is. If you visit a lot of companies websites and get a 404, you will get a list of possible alternatives.

      A 404 is on a webserver that already exists, that is running an http server and has the DNS properly configured.

      Here is a better survey:
      1. Do you know the difference between a 404 and NXDOMAIN error?
      2. If you answered "No" to question 1, do not participate in the rest of this survey.
      3. Do you have your email MTA verifying
  • "Prior to ICANN's October 3 directive to shut down the service, Site Finder had
    been used more than 48 million times by Internet users to get where they want to go online."


    ...as if they all chose to go to Site Finder instead of directly where they intended to go. I'm generally pro-business and pro-creativity, but this is a despicable exploitation of people making honest mistakes. IMHO, this should warrant a DOJ investigation.

  • Let's see if we can knock his approval rating down a peg or two more (look what happened in September, /. effect?). Vote [forbes.com]
  • Last time when Verisign sprung this on Internet users, for the most part, people worked around them. The changes to BIND were not exclusive to Verisign, they just tried to address what they considered to be a flaw exposed by Verisign. This time is different. ICANN has told them not to do it, and they're still going to do it. This time, it's time for a punitive reaction.

    Here's what I propose. If you write software that interacts with DNS keep track of how often Verisign hijacks a non-existant DNS en

  • I have 5 domains registered with netsol. Can anyone reccomend another registrar that I can easily transfer my domains to? I will make it very clear to verisign why I'm moving my domains away from them, and i suggest anyone else do the same.

    • I've had good luck with GoDaddy.com for my domains.
    • Dotster.com floats my boat. They make it very easy to transfer a domain to them. Of course, Verislime still gets $6 of that transaction to publish the record in the root zones.
      -russ
    • I'll second the GoDaddy.com recommendation. They have a history of lowering prices while adding services, and when you write tech support, a Real Human answers.

      And if you just want to tweak netsol's ass, godaddy is one of their primary "let's see if we can hijack their customers" targets.

  • by Saint Stephen ( 19450 ) on Thursday October 16, 2003 @09:22AM (#7228968) Homepage Journal
    Verisign's statement is probably true: Many users (excepting myself) would probably prefer being offered alternative instead of an error message.

    However, the proper place to implement this is at the browser level, not at the network level. So, you can grant their statement is true but it doesn't justify their case.

    • Yup, I'm with you. I think a search engine like Persian Kitty [persiankitty.com] to help me find what I was probably looking for in the first place would be nice :-)
    • Actually, my experience has been that if a non-geek user gets a "no DNS" error, they soon figure out that they mistyped something. However, if they get a fancy alternative (like Verisign's SiteFinder page) they make the assumption that their typing was fine, but that the site they wanted has gone away.

      So even tho something like SiteFinder (even at the browser level) might not look as "scary" as the "No DNS" error, I think it does more harm to these users' actual ability to use the web.

      There are still peop
  • by DuckDuckBOOM! ( 535473 ) * on Thursday October 16, 2003 @09:24AM (#7228991)
    how a company can commission an "independent" survey that yields exactly the results the company wants, regardless of the degree to which those results contradict common experience / knowledge.

    The second (article || press release) yields a clue as to how it was done this time:

    "As a heavy but non-technical computer user it has been extremely frustrating for me to encounter 404 errors. Naturally, they happen at the busiest times," said Roy S. Lahet, vice president of Planning for Mercy Behavioral Health. . .It is difficult for me to see a downside to this user friendly enhancement." (emphasis added)

    Somehow I suspect that the people who don't find 404s "extremely frustrating" and do have the knowledge to "see a downside to this...enhancement" weren't part of the survey. So 53% of clueless PHBs think SiteFinder "improves the Internet". BFD.*

    .

    * "Big Furry Deal." - Dogbert

    • I want to be in Roy S. Lahet's "Vice President of Planning for Mercy Behavioral Health" job. At the "busiest times" of his day, he has time to randomlyy type URLs into Internet Explorer (or maybe AOL. You can never tell.) Plus, he can't even type, or he never would have found SiteFinder in the first place.

    • As a heavy but non-technical computer user it has been extremely frustrating for me to encounter 404 errors.

      I have noticed, during all this Verisign SiteFinder nonsense, that many people who should know better don't seem to have any idea what a 404 error is. (Not referring to the parent poster, of course, but many others.)

      404 isn't what you get when you type in a non-existent domain. That depends on your browser. Error 404 is an HTTP status code that a real live webserver returns when you request a d

  • by An Onerous Coward ( 222037 ) on Thursday October 16, 2003 @09:27AM (#7229034) Homepage
    I think we should have Microsoft crusherize them.

    Next patch to Internet Explorer, they should throw in some code that brings up their own search page whenever a domain name resolves to Verisign's computers.

    I have few complaints with Microsoft's service, because the behavior is happening at the application level, not the infrastructure level. I mean, what good is having a 95% browser share if you can't smack down the little bastards that try to muscle in on your turf? :)
    • here here! Right on! Why not encourage MS to do what they're good at, to both their benefit and ours? This is exactly where capitalism should step in and fix this mess.
  • The award for the ownership of the most packet-filtered IP address in the world, previously held by Mr. Spa Malaur - a mail server operator from China, has been awarded to Verisign.
  • Big deal... it's not like I removed the firewall rules from the last time or anything... Once a spammer, always a spammer.
  • ...that Verisign is selling off Network Solutions [verisign.com]. Sitefinder becomes, then, an abuse of network infrastructure to prop up, based on who's buying the company [bizjournals.com], a troubled business. Shame on that.
  • Your browser should decide what to do if it encounters a 404 error, not the DNS server.

  • Gotta love Verisign's attitude about this whole thing:

    ---
    "Larson suggested that "you guys don't think consumers are relevant" and that committee members were unduly focused on the travails of network operators affected by the Site Finder changes.

    "We're going to have to stop this discussion and turn to a different venue," Larson said."
    ---

    Of course users are important. But the opinions of those in the trenches making things work is more important. Think of it this way:

    What if a car maker declared to its c
  • A poll of 1000 interactive users

    In another story, random members of the families of high ranking Verisign executives were asked about their days. "We spend so much time on the phone now that we have little free time." was a frequently heard complaint. "But I guess we can't get on the Do Not Call list really as the callers all seem to be doing polls and they're all about Verisign. I a bit of responsibility to answer their questions because of my family relationship."

    Those interviewed said they'd ne

  • The present root servers only serve that purpose because we (who have name servers) allow them to. There is a file that comes with recursive name servers that "seeds" them to know where the root servers are (you have to start with some IP addresses). Many people might not yet be aware, but there are separate servers for the "." zone (the root), and top level domains (TLDs) like ".com" (more correctly "com."). It is the root zone that delegates authority to the top level domain servers. By configuring yo

  • Here in Wyoming, we have an old expression which says that a bull "services" a cow. Verisign is "servicing" the Internet community in the same way, by effectively grabbing every unused ".com" or ".net" domain name for its own profit.

    It's worth noting that "ordinary" typosquatters have to pay 7 to 35 dollars a year per domain. Given all the possible names on which Verisign can squat, how much money is it looting from users of the Net? Perhaps it should be required to contribute that amount to a worth Inter

  • I looked at the T&Cs for Sitefinder [verisign.com], and decided that I didn't like them (I disliked parts 4,6,7,8,9,12,13 and 14). Since part 10 tells me that my sole remedy is to stop using Sitefinder, I contacted Verisign to ask how to either amend the T&Cs to suit me, or stop using Sitefinder to handle mistyped domains. Their answer? Don't mistype domains.

    I doubt that they could enforce their T&Cs on me, since I'm not based in the US, but I personally dislike the idea that I can be obliged to accept a cont


  • Me, or your lyin' eyes?

    (As the man said to his wife, on being caught in bed with the housekeeper)

  • That's all there is to it. Infrastructure has to be neutral. That means that HTML must be a platform-neutral standard, DNS resolution must be vendor-neutral, etc., etc.. If your browser doesn't want to follow standards, or if it wants to go to its own page AFTER getting a neutral (Error 404) reply, then so be it. But implement it at the browser level, NOT the infrastructure level.

  • I wrote to Verisign... They posted the following contact information on their press release:
    VeriSign Media Relations: Tom Galvin, tgalvin@verisign.com, 202.973.6600
    VeriSign Investor Relations: Kathleen Bare, kbare@verisign.com, 650.426.3241

    I was quite surprised by the results of their usbility study, so I asked them if they could provide so more data to back up the results. I also provided some other statistics from objective sources that voiced opposite opinions.

    Will this single email be effective? Prob
  • VeriSign says that this will prevent 404 error messages from happening. How did the original SiteFinder prevent that? It prevented NXDOMAIN errors in the .com and .net TLDs, but it never prevented 404 errors, as those are handled by each individual webserver and have nothing to do with DNS, but only with not being able to find a file on an already-resolved webserver.

  • From the press release:
    "As a heavy but non-technical computer user it has been extremely frustrating for me to encounter 404 errors. Naturally, they happen at the busiest times," said Roy S. Lahet, vice president of Planning for Mercy Behavioral Health."

    a google search [google.com] for him came up with this picture [mercybehavioral.com] as the second result.
    out there... somewhere... a Verisign PR guy is limping with a smoking gun and wounded foot
  • Sitefinder TOS (Score:4, Informative)

    by scovetta ( 632629 ) on Thursday October 16, 2003 @01:02PM (#7231384) Homepage
    I find it odd that no one has been discussing the Sitefinder TOS [verisign.com]. Specifically, paragraph 6, which states:
    6. Modification by VeriSign.
    At any time VeriSign may modify or terminate these terms of use, its websites and the VeriSign Services and may at any time discontinue your use of the VeriSign Services without any notice to you, and without liability to you, any other user or any third party. Please review these Terms of Use from time to time so that you will be aware of any changes. Your continued use of the VeriSign Services constitutes your agreement to all such terms, conditions, and notices.


    So I can be found to a "Terms of Use" agreement simply by mistyping a domain name? How is this legal? And are there any situations where a user could be caught in violation of this "agreement"?
  • by Wolfier ( 94144 ) on Thursday October 16, 2003 @02:32PM (#7232527)
    I'm ready to run a background wget that surfs a random URL 10 times a second.

    Please join me.

//GO.SYSIN DD *, DOODAH, DOODAH

Working...