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 * -- Robert A. Pickering Jr. Internet Services Manager Cincinnati Bell Telephone rob@fuse.net A Rough Whimper of Insanity (Information Superhighway) PGP key ID: 75CAFF7D 1995/05/09 PGP Fingerprint: B1 63 0C 09 D8 2E 5D 69 BB 61 A2 92 22 37 63 C3 ---------- Forwarded message ---------- Date: Fri, 11 Jul 1997 10:29:45 -0400 (EDT) From: "Robert A. Pickering Jr." <pickerin@Fuse.net> To: bob@mhmh.org Subject: Microsoft domains (fwd) -- Robert A. Pickering Jr. Internet Services Manager Cincinnati Bell Telephone rob@fuse.net A Rough Whimper of Insanity (Information Superhighway) PGP key ID: 75CAFF7D 1995/05/09 PGP Fingerprint: B1 63 0C 09 D8 2E 5D 69 BB 61 A2 92 22 37 63 C3 ---------- Forwarded message ---------- Date: Fri, 11 Jul 1997 10:26:39 -0400 (EDT) From: "Christopher J. Utley" <cutley@fuse.net> To: fusers@fuse.net, operations@fuse.net Subject: Microsoft domains 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 * -- Christopher J. Utley Webmaster Cincinnati Bell Telephone chris@fuse.net
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... -- Shields, CrossLink.
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 On 14 Jul 1997, Michael Shields wrote:
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... -- Shields, CrossLink.
-- Robert A. Pickering Jr. Internet Services Manager Cincinnati Bell Telephone rob@fuse.net A Rough Whimper of Insanity (Information Superhighway) PGP key ID: 75CAFF7D 1995/05/09 PGP Fingerprint: B1 63 0C 09 D8 2E 5D 69 BB 61 A2 92 22 37 63 C3
"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:
However, the facts still stand. InterNIC registered the domains to the Microsoft nameservers, without having to clear it. That concerns me. -- Unsolicited commercial/propaganda email subject to legal action. Under US Code Title 47, Sec.227(a)(2)(B), Sec.227(b)(1)(C), and Sec.227(b)(3)(C), a State may impose a fine of not less than $500 per message. Read the full text of Title 47 Sec 227 at http://www.law.cornell.edu/uscode/47/227.html
On Mon, Jul 14, 1997 at 02:11:55PM -0400, Robert A. Pickering Jr. wrote:
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.
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 -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Unsolicited Commercial Emailers Sued The Suncoast Freenet "People propose, science studies, technology Tampa Bay, Florida conforms." -- Dr. Don Norman +1 813 790 7592
Robert A. Pickering Jr. was known to have said:
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.
We recently had a downstream customer of ours tell his customer that it was okay to use our nameservers as his secondary for his domains. About 60 of them. The InterNIC appears to have no clear policy on removing the NS records that point to an unwilling DNS server. At one time I actually sent a message off to questions(?)@internic.net on this issue, but never received a response. Our solution was to provide empty DNS records to prevent lame delegation problems.
-Rob
-- Jeffrey Haas "He that breaks a thing to find out what it is has elezar@pfrc.org left the paths of wisdom." (Or works for Fermilab...)
We recently had a downstream customer of ours tell his customer that it was okay to use our nameservers as his secondary for his domains. About 60 of them.
The InterNIC appears to have no clear policy on removing the NS records that point to an unwilling DNS server. At one time I actually sent a message off to questions(?)@internic.net on this issue, but never received a response.
Our solution was to provide empty DNS records to prevent lame delegation problems.
This discussion has taken place before. I believe the most creative solution was submitted by a DNS administrator who simply pointed "www" in the unwelcome domain to some disreputable site. Now, shouldn't this discussion be taken to some *other* place?
participants (6)
-
Jay R. Ashworth -
Jeffrey Haas -
Mark Borchers -
Robert A. Pickering Jr. -
shields＠crosslink.net -
Stephen Sprunk