ICANNWatch
 
  Inside ICANNWatch  
Submit Story
Home
Lost Password
Preferences
Site Messages
Top 10 Lists
Latest Comments
Search by topic

Our Mission
ICANN for Beginners
About Us
How To Use This Site
ICANNWatch FAQ
Slash Tech Info
Link to Us
Write to Us

  Useful ICANN sites  
  • ICANN itself
  • Bret Fausett's ICANN Blog
  • Internet Governance Project
  • UN Working Group on Internet Governance
  • Karl Auerbach web site
  • Müller-Maguhn home
  • UDRPinfo.com;
  • UDRPlaw.net;
  • CircleID;
  • LatinoamerICANN Project
  • ICB Tollfree News

  •   At Large Membership and Civil Society Participation in ICANN  
  • icannatlarge.com;
  • Noncommercial Users Constituency of ICANN
  • NAIS Project
  • ICANN At Large Study Committee Final Report
  • ICANN (non)Members page
  • ICANN Membership Election site

  • ICANN-Related Reading
    Browse ICANNWatch by Subject

    Ted Byfied
    - ICANN: Defending Our Precious Bodily Fluids
    - Ushering in Banality
    - ICANN! No U CANN't!
    - roving_reporter
    - DNS: A Short History and a Short Future

    David Farber
    - Overcoming ICANN (PFIR statement)

    A. Michael Froomkin
    - When We Say US™, We Mean It!
    - ICANN 2.0: Meet The New Boss
    - Habermas@ discourse.net: Toward a Critical Theory of Cyberspace
    - ICANN and Anti-Trust (with Mark Lemley)
    - Wrong Turn in Cyberspace: Using ICANN to Route Around the APA & the Constitution (html)
    - Form and Substance in Cyberspace
    - ICANN's "Uniform Dispute Resolution Policy"-- Causes and (Partial) Cures

    Milton Mueller
    - Ruling the Root
    - Success by Default: A New Profile of Domain Name Trademark Disputes under ICANN's UDRP
    - Dancing the Quango: ICANN as International Regulatory Regime
    - Goverments and Country Names: ICANN's Transformation into an Intergovernmental Regime
    - Competing DNS Roots: Creative Destruction or Just Plain Destruction?
    - Rough Justice: A Statistical Assessment of the UDRP
    - ICANN and Internet Governance

    David Post
    - Governing Cyberspace, or Where is James Madison When We Need Him?
    - The 'Unsettled Paradox': The Internet, the State, and the Consent of the Governed

    Jonathan Weinberg
    - Sitefinder and Internet Governance
    - ICANN, Internet Stability, and New Top Level Domains
    - Geeks and Greeks
    - ICANN and the Problem of Legitimacy

    Highlights of the ICANNWatch Archive
    (June 1999 - March 2001)


     
    This discussion has been archived. No new comments can be posted.
    What's in .NAME? 5000+ .NAME Registrations Not Conforming to .NAME Restrictions | Log in/Create an Account | Top | 185 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Threshold:
    Check box to change your default comment view
    The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
    GNR'S OWN LISTS RE WHAT ICANN AND ICANN'T REGISTER
    by ANNODOMINI2000 (reversethis-{KU.OC.OOHAY} {ta} {D0002DA}) on Friday May 31 2002, @02:24PM (#6648)
    User #3359 Info | http://www.ad2000d.co.uk/
    (SOURCE: BulkRegister)


    .Name reserved domains [page title]


    All second-level domain names (eg. johndoe.name, janedoe.name) are reserved.


    The following strings have been reserved by ICANN and cannot be used as either the second-level or the third-level component of a .NAME domain name or .NAME email address:

    aso
    dnso
    icann
    internic
    pso
    afrinic
    apnic
    arin
    example
    gtld-servers
    iad
    iana
    iana-servers
    iesg
    ietf
    irtf
    istf
    lacnic
    latnic
    rfc-editor
    ripe
    root-servers


    The following strings have been reserved by the Registry and cannot be used as the second-level component of a .NAME domain name or .NAME email address:


    celebrity
    cert
    certificate
    directory
    dns
    dotname
    famous
    findyour
    findyourfamily
    findyourname
    finger
    ftp
    getyour
    getyourname
    gopher
    hostmaster
    imap
    ldap
    login
    myname
    namedomain
    nameregistry
    nntp
    no1
    ntp
    pop
    pop3
    registeryour
    registeryourname
    registry
    scp
    security
    smtp
    snmp
    telnet
    thefamous
    thenamedomain
    thenameregistry
    yourname
    zone
    global
    globalregistry
    gnr
    theglobal
    theglobalname
    theglobalnameregistry
    theglobalregistry


    The following strings have been reserved by the Registry and cannot be used as the third-level component of a .NAME domain name or .NAME email address:


    dir
    directory
    email
    genealogy
    http
    mail
    mx
    mx[followed by a number from 0 to 100] ([0-10] and [11-100])
    ns
    ns[followed by a number from 0 to 100] ([0-10] and [11-100])
    wap
    www
    www[followed by a number from 0 to 100] ([0-10] and [11-100])
    administrator
    hostmaster
    postmaster
    complaints
    mailer-daemon
    abuse
    root
    webmaster
    infomaster


    All single character second-level domains (eg. jane.z.name) are reserved.


    All two character second-level domains (eg. joe.mr.name) are reserved.


    All second-level domains comprised of just numbers and hyphens (eg. joe.123.name, john.9-1-1.name) are reserved.


    All second-level or third-level domains with hyphens in the 3rd and 4th positions (eg. jane-john.doe.name) are reserved.


    The following absolute domain names are not available for registration


    Jesus.Christ.name
    Santa.Claus.name


    -------------------------------------------------


    Quite clearly, then, one be be forgiven for the assumption of believing that as certain generic names are not allowed to be registered, conversely, therefore, others generic names ARE allowable to be registered!
    [ Reply to This | Parent ]
    curiouser.curiouser.name
    by fnord (groy2kNO@SPAMyahoo.com) on Friday May 31 2002, @04:47PM (#6665)
    User #2810 Info
    ANNODOMINI2000 writes:

    (SOURCE: BulkRegister) [...] mucho snippage.
    Welly welly well, look at what we have here. Acting on an hunch that Adrian is determined to be caught and gives us clues in all his verbiage, on those rare occasions when he isn't outright admitting to breaking the rules, I thought I'd try WHOIS bulk.register.name:

    Domain Name: bulk.register.name
    Sponsoring Registrar: BulkRegister.com
    Domain Status: ok
    Registrant ID: CT:AP281
    Registrant Organization: AD 2000 D . COM
    Registrant Name: Adrian Paul MILES
    Registrant Address: c/o 78 Bright Street, Whitmore Reans,
    Registrant City: Wolverhampton WV1 4AS
    Registrant State/Province: -
    Registrant Country: UNITED KINGDOM
    Registrant Postal Code: -
    Admin ID: CT:BR332
    Admin Organization: Bulk Register
    Admin Name: BULK REGISTER
    Admin Address: 10 East Baltimore Street, Suite 1500
    Admin City: Baltimore
    Admin State/Province: MD
    Admin Country: UNITED STATES
    Admin Postal Code: 21202
    Admin Phone Number: +1.8004761879
    Admin Email: ad2000d@yahoo.co.uk
    Tech ID: CT:BR332
    Tech Organization: Bulk Register
    Tech Name: BULK REGISTER
    Tech Address: 10 East Baltimore Street, Suite 1500
    Tech City: Baltimore
    Tech State/Province: MD
    Tech Country: UNITED STATES
    Tech Postal Code: 21202
    Tech Phone Number: +1.8004761879
    Tech Email: ad2000d@yahoo.co.uk
    Billing ID: CT:BR332
    Billing Organization: Bulk Register
    Billing Name: BULK REGISTER
    Billing Address: 10 East Baltimore Street, Suite 1500
    Billing City: Baltimore
    Billing State/Province: MD
    Billing Country: UNITED STATES
    Billing Postal Code: 21202
    Billing Phone Number: +1.8004761879
    Billing Email: ad2000d@yahoo.co.uk
    Name Server: ns3.hostsvr.com
    Name Server: ns4.hostsvr.com
    Created On: 2002-03-08
    Expires On: 2003-03-12
    Updated On: 2002-03-08

    All bulkregister, apparently including the admin, tech and billing contact ID of CT:BR332 (run that handle thru the .name WHOIS and you get bulkregister), and including the name servers, but perhaps not including the email addy. Sooo, either bulkregister is in on this with Adrian, or he might soon be having some trouble with his registrar as well. -g

    [ Reply to This | Parent ]
    Re: GNR'S OWN LISTS RE WHAT ICANN AND ICANN'T REGI
    by ANNODOMINI2000 (reversethis-{KU.OC.OOHAY} {ta} {D0002DA}) on Friday May 31 2002, @03:15PM (#6653)
    User #3359 Info | http://www.ad2000d.co.uk/
    Not idiotic, oh no, just logical and common-sense - please don't insult my intelligence in future, thank you.

    Just for the record, IF either GNR, ICANN - or anyone else - tried to cancel ANY of my domain names (other than through the correct ERDRP or UDRP Procedures), I would not hesitate in suing them in the High Courts of England.
    [ Reply to This | Parent ]
  • 1 reply beneath your current threshold.

  • Search ICANNWatch.org:


    Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
    You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com