- Test - lists.nanog.org

secondary dns
by Steven J. Sobol 15 Mar '99

15 Mar '99

I'm looking for someone to do secondary DNS for some domains that I host. Preferably this person should not be connected directly to any of the backbones I'm connected to. I will, of course, be happy to return the favor. Thanks. -- Steve Sobol sjsobol(a)nacs.net (AKA support(a)nacs.net and abuse(a)nacs.net) "The world is headed for mutiny/When all we want is unity" --Creed, "One"

1 0

InterNIC - We put the "I" in incompetent.
by John Fraizer 15 Mar '99

15 Mar '99

Hello boys and girls. The time is now 0800 EST and of course, whois is still screwed. [rs.internic.net] Registrant: EnterZone.Net (ENTERZONE2-DOM) 604 East Rich Street Columbus, OH 43215 US Domain Name: ENTERZONE.NET Record last updated on 09-May-97. Database last updated on 13-Mar-99 23:57:32 EST. Domain servers in listed order: NS1.ENTERZONE.NET 209.41.244.5 NS2.ENTERZONE.NET 209.41.244.6 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 Lets see... Where do we begin... 1) They lost the data from our update. >From: Domain Registration Role Account <domreg(a)internic.net> >Message-Id: <199903121048.FAA03704(a)mts2.internic.net> >Subject: Re: [NIC-990310.2ebf] ENTERZONE.NET >Date: Fri, 12 Mar 1999 05:48:48 -0500 (EST) >Reply-To: domreg(a)internic.net >To: John.Fraizer(a)EnterZone.Net >X-Mailer: fastmail [version 2.4 PL24alpha4] >X-UIDL: e1f57853ffcc7b0ad65532566d6484df > >The updates, of the domain name shown below, have been completed. If you >wish to make changes to this domain in the future, please submit a Domain >Name Registration Agreement to: > > HOSTMASTER(a)INTERNIC.NET > >Please write "modify" on line 0a. > >All requests completed before 19:00 Eastern time will be included in the >root server update. The root zone files are updated 7 days a week. These >changes should be visible in our Whois database the following day. > >If you wish to make changes to the domain record, contact record, host >record or the registrant name, please use the following URL to complete >the proper form: > > http://rs.internic.net/help/templates.html > >Network Solutions is not an agent or representative of your Internet >Service Provider, web-hosting company, or other organizations with which >you have contracted for Internet-related services. This change to your >domain name record does not amend, modify, or otherwise affect the terms >and conditions of any agreement(s) you may have with third parties. > >Network Solutions, Inc. >E-mail: hostmaster(a)internic.net >Phone: 703-742-4777(Monday-Friday 7:00am to 9:00pm Eastern Time) >Fax: 703-742-9552 >================================================================ > > >EnterZone.Net (ENTERZONE2-DOM) > 6227 Headley Road > Gahanna, OH 43230 > US > > Domain Name: ENTERZONE.NET > > Administrative Contact: > Fraizer, John (JF1998) John.Fraizer(a)ENTERZONE.NET > +1 614 316-2708 > Technical Contact: > Network Operations Center (NOC179-ORG) noc(a)ENTERZONE.NET > +1 614 316-2708 > Billing Contact: > Network Operations Center (NOC179-ORG) noc(a)ENTERZONE.NET > +1 614 316-2708 > > Record last updated on 12-Mar-99. > Domain servers in listed order: > > NS1.ENTERZONE.NET 209.41.244.5 > NS2.ENTERZONE.NET 209.41.244.6 > >========================================================================= Why do any of even take the time to keep our records up to date when they just go lose them, corrupt them, ignore them? 2) They took the POC information out of the display both from rwhois and telnet. Just how are we supposed to find the POCs for a domain now? 3) They are causing service effecting outages with NO NOTICE to US, their customers. This is getting real %^&*# old, real %^*# fast. I wish they would start spending my $35/yr per domain on clue. ------------------------------------------------------------------ ML.ORG is gone. Check out http://www.EZ-IP.Net - It's *FREE* ------------------------------------------------------------------ Get your *FREE* Parked Domain account at http://www.EZ-Hosting.Com ------------------------------------------------------------------ John Fraizer | __ _ | The System Administrator | / / (_)__ __ ____ __ | The choice mailto:John.Fraizer@EnterZone.Net | / /__/ / _ \/ // /\ \/ / | of a GNU http://www.EnterZone.Net/ | /____/_/_//_/\_,_/ /_/\_\ | Generation PGP Key fingerprint = 7DB6 1CA2 DAA6 43DA 3AAF 44CD 258C 3D7E B425 81A8

13 19

Re: RE:Whois Internic Toast
by Vadim Antonov 15 Mar '99

15 Mar '99

>> Can I please have a new Domain Provider !!!! >we will all get what we deserve. I always had an opinion that backbone ISPs should form a consortium and take over the domain mess. They have a pretty good track record of getting contentious issues resolved in a rational and workable manner. Actually, CIX seems to be well-positioned to do exactly that. Now, telcos have way too many lawyers who are loath to work a little too harder to be on the right side of the Sherman Act, but i suspect their ISP departments by now feel the pain - how many customers bother their help desks to get their DNS issues resolved? --vadim

1 0

routing registries question
by hhui＠arcfour.com 15 Mar '99

15 Mar '99

naive question: I just noticed that ARIN has a routing registry and was wondering what that does for me. I notice it doesn't mirror RADB very well. does it supercede IRR/RADB or is it just another fun tool? (this is not a political question) -h

2 1

Re: InterNIC - We put the "I" in incompetent.
by George Herbert 14 Mar '99

14 Mar '99

Michael Dillon <michael(a)memra.com> wrote: >On Sun, 14 Mar 1999, I Am Not An Isp wrote: >> >> NS1.ENTERZONE.NET 209.41.244.5 >> >> NS2.ENTERZONE.NET 209.41.244.6 >> > >> >Hmm... same subnet... >> >> Michael, you should know better than that. I do not see a subnet mask on >> these IP addresses. There is nothing stopping a Network Operator from >> making these /32s and putting them on different networks. > >Nothing except community consensus that it is a *BAD* thing to pollute the >global routing table with lots of long prefixes. Could be internally divided within a single external announcement from one AS. However, I think we all know this is nitpicking and the odds that these systems are further apart than about 20 feet approach zero. -george william herbert gherbert(a)crl.com

1 0

internic fwiw
by Jared Mauch 14 Mar '99

14 Mar '99

I just watched a domain reg go through for something hosted on my dns servers. follow-up to /dev/null or your local bit repositry. -- Jared Mauch | pgp key available via finger from jared(a)puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.

1 0

sorry about that
by Becki Kain 14 Mar '99

14 Mar '99

someone else (ie: not me) decided to register furph for internic.net and yes, the internic refused the request, stating that it was already registered. 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)

1 0

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