March 1999 - Test - lists.nanog.org

Re: need i say more?
by mark＠vielle.datasys.net 14 Mar '99

14 Mar '99

: "melinda b. thompson" wrote: : > : > No match for "INTERNIC.NET". : : Makes me feel marginally better about several of my domains not being : located today. Gotta wonder... Gee, people: the root name servers still look good, right? As long as these changes don't get propogated and the NIC comes back up soon, nobody's going to get hurt. Sure, it's annoying; but for valid domains with running DNS and accurate SOAs, we still have a working DNS, and we still have POCs (given in the SOA). Am I wrong? --- Mark R. Lindsey, mark(a)datasys.net Internet Engineering, DSS Online

2 1

Re: need i say more?
by melinda b. thompson 14 Mar '99

14 Mar '99

Robert E. Seastrom dropped this into my mailbox: >have you sent in a registration form yet? > > ---rob > > >"melinda b. thompson" <ima(a)badhabit.org> writes: > >> No match for "INTERNIC.NET". (snip) To: "melinda b. thompson" <ima(a)badhabit.org> From: hostmaster(a)internic.net Subject: Re: [NIC-990314.5662] Re: NEW DOMAIN internic.net again...need i say more? :D ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ life is a constant stream of people coming into and out of your life... sometimes you get to grab hold of one or two of them for a while... ima(a)badhabit.org http://www.ircd.com/meldatlist.html PGP Fingerprint: 5E9F 31EF DF11 A3EF F3E4 CB3C 9F42 2EC8 BCD0 C607 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Re: NEW DOMAIN internic.net
by Becki Kain 14 Mar '99

14 Mar '99

Becki Kain beckers(a)furph.com -- furph, Inc. WWW/Unix/Windows Solutions 734-513-7763 (voice) info(a)furph.com http://www.furph.com 734-513-7759 (FAX) On Sun, 14 Mar 1999 hostmaster(a)internic.net wrote: > ---------------------------------------------------- > This is the Domain Name Registration Agreement you > recently created. > In order to complete this action, > > YOU MUST E-MAIL THIS FORM TO: hostmaster(a)internic.net > > After you e-mail this form, you should receive an auto-reply > with a tracking number. You must use that number in the > Subject of any future messages you send regarding > this registration action. > Once this registration action is completed you will receive > a notification via e-mail. > > [ URL http://rs.internic.net/cgi-bin/domain ] [ 03/98 ] > [ URL ftp://rs.internic.net/templates/domain-template.txt ] [ 03/98 ] > > ******* Please DO NOT REMOVE Version Number or Sections A-Q ******** > > Domain Version Number: 4.0 > > ******* Email completed agreement to hostmaster(a)internic.net ******* > > NETWORK SOLUTIONS, INC. > > DOMAIN NAME REGISTRATION AGREEMENT > > > A. Introduction. This domain name registration agreement > ("Registration Agreement") is submitted to NETWORK SOLUTIONS, INC. > ("NSI") for the purpose of applying for and registering a domain name > on the Internet. If this Registration Agreement is accepted by NSI, > and a domain name is registered in NSI's domain name database and > assigned to the Registrant, Registrant ("Registrant") agrees to be > bound by the terms of this Registration Agreement and the terms of > NSI's Domain Name Dispute Policy ("Dispute Policy") which is > incorporated herein by reference and made a part of this Registration > Agreement. This Registration Agreement shall be accepted at the > offices of NSI. > > B. Fees and Payments. > > 1) Registration or renewal (re-registration) date through March 31, 1998: > Registrant agrees to pay a registration fee of One Hundred United States > Dollars (US) as consideration for the registration of each new domain > name or Fifty United States Dollars (US) to renew (re-register) an > existing registration. > 2) Registration or renewal date on and after April 1, 1998: Registrant > agrees to pay a registration fee of Seventy United States Dollars (US) > as consideration for the registration of each new domain name or the > applicable renewal (re-registration) fee (currently Thirty-Five United > States Dollars (US)) at the time of renewal (re-registration). > 3) Period of Service: The non-refundable fee covers a period of two (2) > years for each new registration, and one (1) year for each renewal, > and includes any permitted modification(s) to the domain name record > during the covered period. > 4) Payment: Payment is due to Network Solutions within thirty (30) > days from the date of the invoice. > > C. Dispute Policy. Registrant agrees, as a condition to > submitting this Registration Agreement, and if the Registration > Agreement is accepted by NSI, that the Registrant shall be bound by > NSI's current Dispute Policy. The current version of the Dispute > Policy may be found at the InterNIC Registration Services web site: > "http://www.netsol.com/rs/dispute-policy.html". > > D. Dispute Policy Changes or Modifications. Registrant agrees > that NSI, in its sole discretion, may change or modify the Dispute > Policy, incorporated by reference herein, at any time. Registrant > agrees that Registrant's maintaining the registration of a domain name > after changes or modifications to the Dispute Policy become effective > constitutes Registrant's continued acceptance of these changes or > modifications. Registrant agrees that if Registrant considers any such > changes or modifications to be unacceptable, Registrant may request > that the domain name be deleted from the domain name database. > > E. Disputes. Registrant agrees that, if the registration of its > domain name is challenged by any third party, the Registrant will be > subject to the provisions specified in the Dispute Policy. > > F. Agents. Registrant agrees that if this Registration Agreement > is completed by an agent for the Registrant, such as an ISP or > Administrative Contact/Agent, the Registrant is nonetheless bound as a > principal by all terms and conditions herein, including the Dispute > Policy. > > G. Limitation of Liability. Registrant agrees that NSI shall have > no liability to the Registrant for any loss Registrant may incur in > connection with NSI's processing of this Registration Agreement, in > connection with NSI's processing of any authorized modification to the > domain name's record during the covered period, as a result of the > Registrant's ISP's failure to pay either the initial registration fee > or renewal fee, or as a result of the application of the provisions of > the Dispute Policy. Registrant agrees that in no event shall the > maximum liability of NSI under this Agreement for any matter exceed > Five Hundred United States Dollars (US). > > H. Indemnity. Registrant agrees, in the event the Registration > Agreement is accepted by NSI and a subsequent dispute arises with any > third party, to indemnify and hold NSI harmless pursuant to the terms > and conditions contained in the Dispute Policy. > > I. Breach. Registrant agrees that failure to abide by any > provision of this Registration Agreement or the Dispute Policy may be > considered by NSI to be a material breach and that NSI may provide a > written notice, describing the breach, to the Registrant. If, within > thirty (30) days of the date of mailing such notice, the Registrant > fails to provide evidence, which is reasonably satisfactory to NSI, > that it has not breached its obligations, then NSI may delete > Registrant's registration of the domain name. Any such breach by a > Registrant shall not be deemed to be excused simply because NSI did > not act earlier in response to that, or any other, breach by the > Registrant. > > J. No Guaranty. Registrant agrees that, by registration of a > domain name, such registration does not confer immunity from objection > to either the registration or use of the domain name. > > K. Warranty. Registrant warrants by submitting this Registration > Agreement that, to the best of Registrant's knowledge and belief, the > information submitted herein is true and correct, and that any future > changes to this information will be provided to NSI in a timely manner > according to the domain name modification procedures in place at that > time. Breach of this warranty will constitute a material breach. > > L. Revocation. Registrant agrees that NSI may delete a > Registrant's domain name if this Registration Agreement, or subsequent > modification(s) thereto, contains false or misleading information, or > conceals or omits any information NSI would likely consider material > to its decision to approve this Registration Agreement. > > M. Right of Refusal. NSI, in its sole discretion, reserves the > right to refuse to approve the Registration Agreement for any > Registrant. Registrant agrees that the submission of this Registration > Agreement does not obligate NSI to accept this Registration Agreement. > Registrant agrees that NSI shall not be liable for loss or damages > that may result from NSI's refusal to accept this Registration > Agreement. > > N. Severability. Registrant agrees that the terms of this > Registration Agreement are severable. If any term or provision is > declared invalid, it shall not affect the remaining terms or > provisions which shall continue to be binding. > > O. Entirety. Registrant agrees that this Registration Agreement > and the Dispute Policy is the complete and exclusive agreement between > Registrant and NSI regarding the registration of Registrant's domain > name. This Registration Agreement and the Dispute Policy supersede all > prior agreements and understandings, whether established by custom, > practice, policy, or precedent. > > P. Governing Law. Registrant agrees that this Registration > Agreement shall be governed in all respects by and construed in > accordance with the laws of the Commonwealth of Virginia, United > States of America. By submitting this Registration Agreement, > Registrant consents to the exclusive jurisdiction and venue of the > United States District Court for the Eastern District of Virginia, > Alexandria Division. If there is no jurisdiction in the United States > District Court for the Eastern District of Virginia, Alexandria > Division, then jurisdiction shall be in the Circuit Court of Fairfax > County, Fairfax, Virginia. > > Q. This is Domain Name Registration Agreement Version > Number 4.0. This Registration Agreement is only for registrations > under top-level domains: COM, ORG, NET, and EDU. By completing > and submitting this Registration Agreement for consideration and > acceptance by NSI, the Registrant agrees that he/she has read and > agrees to be bound by A through P above. > > Authorization > 0a. (N)ew (M)odify (D)elete.........: New Registration > 0b. Auth Scheme.....................: > 0c. Auth Info.......................: > > 1. Comments........................: > > 2. Complete Domain Name............: internic.net > > Organization Using Domain Name > 3a. Organization Name................: furph inc > 3b. Street Address..................: 10058 cavell > 3c. City............................: livonia > 3d. State...........................: mi > 3e. Postal Code.....................: 48150 > 3f. Country.........................: us > > Administrative Contact > 4a. NIC Handle (if known)...........: bk309 > 4b. (I)ndividual (R)ole?............: Individual > 4c. Name (Last, First)..............: > 4d. Organization Name...............: > 4e. Street Address..................: > 4f. City............................: > 4g. State...........................: > 4h. Postal Code.....................: > 4i. Country.........................: > 4j. Phone Number....................: > 4k. Fax Number......................: > 4l. E-Mailbox.......................: > > Technical Contact > 5a. NIC Handle (if known)...........: bk309 > 5b. (I)ndividual (R)ole?............: Individual > 5c. Name(Last, First)...............: > 5d. Organization Name...............: > 5e. Street Address..................: > 5f. City............................: > 5g. State...........................: > 5h. Postal Code.....................: > 5i. Country.........................: > 5j. Phone Number....................: > 5k. Fax Number......................: > 5l. E-Mailbox.......................: > > Billing Contact > 6a. NIC Handle (if known)...........: bk309 > 6b. (I)ndividual (R)ole?............: Individual > 6c. Name (Last, First)..............: > 6d. Organization Name...............: > 6e. Street Address...................: > 6f. City............................: > 6g. State...........................: > 6h. Postal Code.....................: > 6i. Country.........................: > 6j. Phone Number....................: > 6k. Fax Number......................: > 6l. E-Mailbox.......................: > > Prime Name Server > 7a. Primary Server Hostname.........: josephus.furph.com > 7b. Primary Server Netaddress.......: 209.69.35.3 > > Secondary Name Server(s) > 8a. Secondary Server Hostname.......: tigger.erim.org > 8b. Secondary Server Netaddress.....: 209.69.218.27 > > > END OF AGREEMENT > > > For instructions, please refer to: > "http://rs.internic.net/help/instructions.txt" > >

1 0

need i say more?
by melinda b. thompson 14 Mar '99

14 Mar '99

No match for "INTERNIC.NET". The InterNIC Registration Services database contains ONLY non-military and non-US Government Domains and contacts. Other associated whois servers: American Registry for Internet Numbers - whois.arin.net European IP Address Allocations - whois.ripe.net Asia Pacific IP Address Allocations - whois.apnic.net US Military - whois.nic.mil US Government - whois.nic.gov ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ life is a constant stream of people coming into and out of your life... sometimes you get to grab hold of one or two of them for a while... ima(a)badhabit.org http://www.ircd.com/meldatlist.html PGP Fingerprint: 5E9F 31EF DF11 A3EF F3E4 CB3C 9F42 2EC8 BCD0 C607 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

3 2

RE:Whois Internic Toast
by Derrick Bennett 14 Mar '99

14 Mar '99

After taliking to their helpdesk they say this is a major Whois upgrade and will be done at 8:00 am their time. At that time we should get the normal responses back. When asked why they don't notify their customers about changes and outages the response was simply "We don't know if it is an outage or an upgrade but whois is not a required service so there is no service impact". Can I please have a new Domain Provider !!!! Derrick

3 2

InterNIC whois toast
by Troy Davis 14 Mar '99

14 Mar '99

whois is reporting that most domains are nonexistant: > whois root-servers.net [rs.internic.net] No match for "ROOT-SERVERS.NET". The InterNIC Registration Services database contains ONLY non-military and non-US Government Domains and contacts. Other associated whois servers: American Registry for Internet Numbers - whois.arin.net European IP Address Allocations - whois.ripe.net Asia Pacific IP Address Allocations - whois.apnic.net US Military - whois.nic.mil US Government - whois.nic.gov -- Troy Davis

4 3

who is using RPF on peers?
by R.P. Aditya 13 Mar '99

13 Mar '99

Almost a month ago, certain nets of ours (AS10368) lost connectivity to a major provider. The problem was tracked down to the major provider having enabled RPF, or "ip verify unicast reverse-path" in IOS-speak, on one of their private peers with one of our upstreams to whom we don't announce those nets. At the time, I decided not to post a warning to nanog as it appeared to be a mistake and an isolated case. Apparently, the same major provider had/has RPF enabled on other peering interfaces also and one more instances were tracked down in the last 24 hours. Enabling RPF on the "backbone" is not a good idea as long as path-asymmetry exists -- unless you are trying to send a message to an unresponsive peer who is sending you source-spoofed packets. Please take this as an appeal to double-check your use of RPF and restrict it to the "edges" of your network. Thanks, Adi

2 1

Re: (!) Vint Cerf designing network for solar system (!)
by Steve Feldman 13 Mar '99

13 Mar '99

This leads to the obvious (for me, anyway) question of NAP placement. It seems to me that multiple providers on Mars wouldn't want to backhaul traffic all the way to Earth just to talk across the canal... MAE-Mars? Sorry, it's Friday afternoon. :) Steve

6 5

Re: Smurf amp notification script?
by Jeff Weisberg 13 Mar '99

13 Mar '99

| > Does anyone have a script that takes a list of IP addresses, looks | > them up in whois, and mails the contact for them and tells them | > they're a smurf amp (with appropriate pointers to self-help files, | > etc)? | > | > If it can read sorted output from Cisco "sh ip cache flow", that'd be | > a bonus. | | No, but we'd be interested in this if you come across one. Ronald Guilmette's | ipw (www.e-scrub.com/ipw/) is the closest I've seen, and it's unreliable at | best. The enclosed hack worked last time I tried it (but no garuntees). Change occurances of OpNet/op.net to your own name. --jeff #!/usr/local/bin/perl while( <> ){ chop; $net = $_; $email = lookup($net); while( !$email ){ sleep 5; $email = lookup($net); } print "$net <$email>\n"; email( $net, $email ) if $email; sleep 2; } exit; sub lookup { my($net) = @_; my($email, $coord, $netblock); open(W, "whois -h whois.arin.net $net |"); $email = ''; $netblock = ''; $coord = 0; while( <W> ){ chop; if( $coord ){ $coord = 0; ($email) = /.*\)\s*(.*)/; last; } $coord = 1 if /Coordinator/; if( /NETBLK-/ ){ $netblock = $_; $netblock =~ s/.*$//; $netblock =~ s/$.*//; } } return $email if $email; return lookup( $netblock ) if $netblock; ''; } sub email { my($net, $email) = @_; open(E, "|sendmail -t"); if( $email =~ /NOWHERE/ ){ print "**** NOWHERE ****\n"; return; } print E <<EOF To: $email From: OpNet NOC <noc\(a)YOURDOMAIN.net> Reply-To: OpNet NOC <noc\(a)YOURDOMAIN.net> Subject: Denial of Service attacks launched through your machines. Netblock: $net Your machines were being used to mount a denial of service attack against one of our machines. This not only uses up our bandwidth but yours. The exact type of attack is typically called a `smurf' attack : A "smurf attack" is a denial-of-service attack which is launched from a network, frequently a dial-up connection, with the intention of burying the victim's network access with packets beyond their ability to carry the traffic load presented. This is accomplished by sending a forged ICMP packet to a smurf amplifier destination, on the broadcast address, bearing the source address of the victim's computer. The smurf amplifier network dutifully responds from all network hosts on that segment, amplifying the transmitted packet by up to 200-fold. These packets are then returned to the victim's computer, swamping its connection and rendering it useless. It is possible to completely destroy host connectivity even on ethernet-speed connections (6x a T1) with just a modem connection to the Internet using this technique. A T1 customer using this technique can bury an OC3 (155mbps) circuit, assuming sufficient amplifier bandwidth can be found. { from http://www.mcs.net/smurf } Some simple changes to your router configurations can keep your machines from being used as smurf amplifiers. More information on smurfs, including what to do about them, can be found at : http://www.quadrunner.com/~chuegen/smurf.txt and http://www.mcs.net/smurf You're receiving this email because you're listed with an IP registry as being the maintainer of one of the networks where I'm seeing ICMP echo requests coming from. I'd greatly appreciate it if you could fix your routers so your networks cannot be abused in this manner. Thanks. -- OpNet Network Operations Staff EOF ; close E; }

2 1

disa.mil or dla.mil contacts?
by Eric Kozowski 12 Mar '99

12 Mar '99

does anyone know a voice contact for disa.mil or dla.mil? i can't get through to whois.nic.mil or the disa.mil or dla.mil mail servers. and, yes randy, this isn't noc(a)disa.mil, but since their servers aren't reachable, noc is the mil nic, i thought i'd ask here.

1 0