Microsoft Registered Domains

Mailman List Mirror (Read Only)
1

I'll admit, the Operations value of this message is a bit low. But,
it does clarify how the InterNIC's use of automation is allowing people
to register domain names against another company, with no trace of
who the culprit may have been.

I thought the correct procedure was to get an ACK/NACK acknowledgement
from the owner of the DNS servers BEFORE going ahead and registering the
domains.

There's also some humor value as well:

-Rob

Some domains registered to Microsoft:

Start: 7/11/97 9:56:21 AM
       Whois user[@]: do weshallprevail.com

       [rs.internic.net.]
       Microsoft Corporation (WESHALLPREVAIL-DOM)
          3635 157th Avenue
          Redmond, WA 98052
          US

          Domain Name: WESHALLPREVAIL.COM

          Administrative Contact:
             MSN Hostmaster (MH37-ORG) msnhst@MICROSOFT.COM
             tel.: 206 882 8080 fax.: 206 703 2641

          Technical Contact, Zone Contact:
             MSN NOC (MN5-ORG) msnnoc@MICROSOFT.COM
             206 882 8080
          Billing Contact:
             MSN Domain Billing (MDB-ORG) msnbill@MICROSOFT.COM
             206 882 8080

          Record last updated on 24-Jun-97.
          Record created on 24-Jun-97.
          Database last updated on 11-Jul-97 04:20:56 EDT.

          Domain servers in listed order:

          ATBD.MICROSOFT.COM 131.107.1.7
          DNS1.MICROSOFT.COM 131.107.1.240
          DNS3.NWNET.NET 192.220.250.7
          DNS4.NWNET.NET 192.220.251.7

       The InterNIC Registration Services Host contains ONLY Internet
Information
       (Networks, ASN's, Domains, and POC's).
       Please use the whois server at nic.ddn.mil for MILNET Information.

       * Whois complete 7/11/97 9:56:40 AM *
       Start: 7/11/97 9:57:12 AM
       Whois user[@]: do RESISTANCE-IS-FUTILE.COM

       [rs.internic.net.]
       Microsoft Corporation (RESISTANCE-IS-FUTILE-DOM)
          3635 157th Avenue
          Redmond, WA 98052
          US

          Domain Name: RESISTANCE-IS-FUTILE.COM

          Administrative Contact:
             MSN Hostmaster (MH37-ORG) msnhst@MICROSOFT.COM
             tel.: 206 882 8080 fax.: 206 703 2641

          Technical Contact, Zone Contact:
             MSN NOC (MN5-ORG) msnnoc@MICROSOFT.COM
             206 882 8080
          Billing Contact:
             MSN Domain Billing (MDB-ORG) msnbill@MICROSOFT.COM
             206 882 8080

          Record last updated on 24-Jun-97.
          Record created on 24-Jun-97.
          Database last updated on 11-Jul-97 04:20:56 EDT.

          Domain servers in listed order:

          ATBD.MICROSOFT.COM 131.107.1.7
          DNS1.MICROSOFT.COM 131.107.1.240
          DNS3.NWNET.NET 192.220.250.7
          DNS4.NWNET.NET 192.220.251.7

       The InterNIC Registration Services Host contains ONLY Internet
Information
       (Networks, ASN's, Domains, and POC's).
       Please use the whois server at nic.ddn.mil for MILNET Information.

       * Whois complete 7/11/97 9:57:32 AM *
       Start: 7/11/97 9:57:50 AM
       Whois user[@]: do BILL-IS-LORD.COM

       [rs.internic.net.]
       Microsoft Corporation (BILL-IS-LORD-DOM)
          3635 157th Avenue
          Redmond, WA 98052
          US

          Domain Name: BILL-IS-LORD.COM

          Administrative Contact:
             MSN Hostmaster (MH37-ORG) msnhst@MICROSOFT.COM
             tel.: 206 882 8080 fax.: 206 703 2641

          Technical Contact, Zone Contact:
             MSN NOC (MN5-ORG) msnnoc@MICROSOFT.COM
             206 882 8080
          Billing Contact:
             MSN Domain Billing (MDB-ORG) msnbill@MICROSOFT.COM
             206 882 8080

          Record last updated on 24-Jun-97.
          Record created on 24-Jun-97.
          Database last updated on 11-Jul-97 04:20:56 EDT.

          Domain servers in listed order:

          ATBD.MICROSOFT.COM 131.107.1.7
          DNS1.MICROSOFT.COM 131.107.1.240
          DNS3.NWNET.NET 192.220.250.7
          DNS4.NWNET.NET 192.220.251.7

       The InterNIC Registration Services Host contains ONLY Internet
Information
       (Networks, ASN's, Domains, and POC's).
       Please use the whois server at nic.ddn.mil for MILNET Information.

       * Whois complete 7/11/97 9:58:08 AM *

2

I'll admit, the Operations value of this message is a bit low.

Well, two of those domains don't exist now and one appears to be
totally unrelated to Microsoft -- so either there were two deletions
and a transfer just now, or else the risk is people forwarding
admittedly marginally relevant things to mailing lists without
checking on the facts.

Our time is the scarcest resource...

3

Michael,

I agree, I should have RE-CHECKED the domains before I sent the
message to the list. I've learned.

However, the facts still stand. InterNIC registered the domains to
the Microsoft nameservers, without having to clear it. That concerns
me.

What if I registered a domain against your nameservers and then
advertised it? What would your nameservers do with the lame delegations?
I've had lame delegations really mess up my DNS servers. They spend all
their time asking the top-level servers, who just point back to them.

-Rob

4

However, the facts still stand. InterNIC registered the domains to
the Microsoft nameservers, without having to clear it. That concerns
me.

Isn't that what Guardian was for?

5

I had a related problem just recently.

tsp.net is about to move. baylink.com and tbtoday.com (among others)
will be taking over the physical hardware, servers, and network
numbers.

So I tried to submit host registrations for ns1. and ns2.baylink.com.

One went through fine, the other disappeared. The _reason_ it
disappeared was that the IP address already was registered... as
tsp-hst (tsp.net).

Hold on, cause this is where it gets pertinent.

I had to call and have the domain reg for tbtoday.com hand walked.
They ran it through... wih tsp.net as one of the nameservers. They
didn't confirm it, although they did carbon the registration approval
to the registered contact for that nameserver.

So, what _is_ their policy supposed to be here?

Cheers,
-- jra

6

"Guardian" only protects the record from modification by unauthorized
users; there is no (publicly known) verification done on the actual
contents of authorized modifications.

This is another facet of NSI no longer checking for SOAs before accepting a
domain.

Stephen

Sez Michael Shields:

Isn't that what Guardian was for?

Sez Robert A. Pickering Jr: