- NANOG - lists.nanog.org

Port 43 Whois Announcement
by Newell, Tom 17 Nov '99

17 Nov '99

An FYI of an operational nature....... --Tom Director of gTLD Programs NSI Registry ########################################## Redirecting Port 43 Whois The following change is being made to comply with the recently negotiated and signed agreements between the U.S. Department of Commerce, ICANN, and NSI. Effective December 1, 1999 Network Solutions will be redirecting port 43 (rs.internic.net) Whois from the NSI Registrar Whois to the NSI Registry Whois. The NSI Registry Whois can currently be found at whois.nsiregistry.net. After this occurs, port 43 Whois will show the following information: domain name, registrar, Whois server, registrar referral URL and the names of the name servers associated with the domain. To obtain registrant and domain name contact information, users will need to refer to the Whois service provided by the registrar for the domain name. Send questions or comments to whois(a)nsiregistry.net.

7 6

Re: Port 43 Whois Announcement
by Dean Anderson 17 Nov '99

17 Nov '99

This isn't nonsense. Its a necessary part of having multiple registrars. This whois is used to avoid namespace collisions between registrars, as well as find the appropriate registrar for a domain. My question (should just test I suppose) is if the rwhois client will automatically query the delegated whois server for the rest of the information. Now that might be useful... --Dean Around 03:40 PM 11/16/1999 -0500, rumor has it that William Allen Simpson said: > >What nonsense is this? > >The registrant and contact information should be in the same >records as the name servers. After all, that's why we called >it "whois", not something else. We want the "who" part, so that >we can contact them! > >Please quote the exact language in the MoU that describes removing >the "who" from whois? > >"Newell, Tom" wrote: >> >> An FYI of an operational nature....... >> >> --Tom >> Director of gTLD Programs >> NSI Registry >> >> ########################################## >> >> Redirecting Port 43 Whois >> >> The following change is being made to comply with the recently >> negotiated and signed agreements between the U.S. Department of >> Commerce, ICANN, and NSI. >> >> Effective December 1, 1999 Network Solutions will be redirecting >> port 43 (rs.internic.net) Whois from the NSI Registrar Whois to >> the NSI Registry Whois. The NSI Registry Whois can currently be >> found at whois.nsiregistry.net. After this occurs, port 43 Whois >> will show the following information: domain name, registrar, Whois >> server, registrar referral URL and the names of the name servers >> associated with the domain. To obtain registrant and domain name >> contact information, users will need to refer to the Whois service >> provided by the registrar for the domain name. >> >> Send questions or comments to whois(a)nsiregistry.net. > >-- > >WSimpson(a)UMich.edu > Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32 > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Plain Aviation, Inc dean(a)av8.com LAN/WAN/UNIX/NT/TCPIP http://www.av8.com ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

2 1

Re: Port 43 Whois Announcement
by nicholas harteau 17 Nov '99

17 Nov '99

As Derek _very_ politely pointed out, I am, in fact, retarded. Derek J. Balling wrote: > I don't know about that... did you follow the directions they thoughtfully > provided for you? > > $ whois -h whois.nsiregistry.net. =wisc.edu > > Whois Server Version 1.1 > > Server Name: WISC.EDU > IP Address: 128.104.30.27 > Registrar: NETWORK SOLUTIONS, INC. > Whois Server: rs.internic.net > Referral URL: www.networksolutions.com > > > > Domain Name: WISC.EDU > Registrar: NETWORK SOLUTIONS, INC. > Whois Server: rs.internic.net > Referral URL: www.networksolutions.com > Name Server: CS.WISC.EDU > Name Server: DNS.CS.WISC.EDU > Name Server: DNS2.ITD.UMICH.EDU > Name Server: DNS2.CS.WISC.EDU > > > NSI can hardly be responsible if WISC.EDU wants to name a host WISC.EDU in > the database. > > I'll let you point out your own mistake on the list, if you so choose. :) > > D > > > > At 06:13 PM 11/16/99 -0600, you wrote: > > >I think they've still got some bugs to work out: > > > >[nrh@squig ~] whois -h whois.nsiregistry.net. wisc.edu > > > >Whois Server Version 1.1 > > > >WISC.EDU > >WISC.EDU > > > >To single out one record, look it up with "xxx", where xxx is one of the > >of the records displayed above. If the records are the same, look them up > >with "=xxx" to receive a full display for each record. > > > > >>> Last update of whois database: Tue, 16 Nov 99 01:16:23 EST <<< > > > >The Registry database contains ONLY .COM, .NET, .ORG, .EDU domains and > >Registrars. > > > > > >Newell, Tom wrote: > > > > > > An FYI of an operational nature....... > > > > > > --Tom > > > Director of gTLD Programs > > > NSI Registry > > > > > > ########################################## > > > > > > Redirecting Port 43 Whois > > > > > > The following change is being made to comply with the recently > > > negotiated and signed agreements between the U.S. Department of > > > Commerce, ICANN, and NSI. > > > > > > Effective December 1, 1999 Network Solutions will be redirecting > > > port 43 (rs.internic.net) Whois from the NSI Registrar Whois to > > > the NSI Registry Whois. The NSI Registry Whois can currently be > > > found at whois.nsiregistry.net. After this occurs, port 43 Whois > > > will show the following information: domain name, registrar, Whois > > > server, registrar referral URL and the names of the name servers > > > associated with the domain. To obtain registrant and domain name > > > contact information, users will need to refer to the Whois service > > > provided by the registrar for the domain name. > > > > > > Send questions or comments to whois(a)nsiregistry.net. > > > >-- > >nicholas harteau > >nrh(a)ikami.com -- nicholas harteau nrh(a)ikami.com

1 0

RE: Port 43 Whois Announcement
by Newell, Tom 16 Nov '99

16 Nov '99

Bill Simpson asked: "Please quote the exact language in the MoU that describes removing the "who" from whois?" The requirement for changing Port 43 whois responses is detailed in Amendment 19, Para 3A as available at the ICANN web site at: http://www.icann.org/nsi/coopagmt-amend19-04nov99.htm 3. InterNIC A. Within six months from the effective date of this amendment (the "Transition Period"), NSI shall transfer the internic.com, internic.org and internic.net SLD names to the Department of Commerce. Beginning within twenty-one days of this amendment and until NSI has completed such transfer, NSI shall provide port 43 Whois access to registry data through rs.internic.net. Such Whois service shall return, in addition to the requested registry data, a message stating: "Domain names in the .com, .net, and .org domains can now be registered with many different competing registrars. Go to http://www.internic.net for detailed information." This requirement was inserted at the request of the registrar community to the ICANN board. The NSI Registry is committed to working within the IETF process towards a more ubiquitous solution (ala draft-faltstrom-whois-02.txt). --Tom -----Original Message----- From: William Allen Simpson [mailto:wsimpson@greendragon.com] Sent: Tuesday, November 16, 1999 3:40 PM To: nanog(a)merit.edu Cc: whois(a)nsiregistry.net Subject: Re: Port 43 Whois Announcement What nonsense is this? The registrant and contact information should be in the same records as the name servers. After all, that's why we called it "whois", not something else. We want the "who" part, so that we can contact them! Please quote the exact language in the MoU that describes removing the "who" from whois? "Newell, Tom" wrote: > > An FYI of an operational nature....... > > --Tom > Director of gTLD Programs > NSI Registry > > ########################################## > > Redirecting Port 43 Whois > > The following change is being made to comply with the recently > negotiated and signed agreements between the U.S. Department of > Commerce, ICANN, and NSI. > > Effective December 1, 1999 Network Solutions will be redirecting > port 43 (rs.internic.net) Whois from the NSI Registrar Whois to > the NSI Registry Whois. The NSI Registry Whois can currently be > found at whois.nsiregistry.net. After this occurs, port 43 Whois > will show the following information: domain name, registrar, Whois > server, registrar referral URL and the names of the name servers > associated with the domain. To obtain registrant and domain name > contact information, users will need to refer to the Whois service > provided by the registrar for the domain name. > > Send questions or comments to whois(a)nsiregistry.net. -- WSimpson(a)UMich.edu Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32

3 2

Sneaking IPv6 onto the Internet???
by Henry R. Linneweh 16 Nov '99

16 Nov '99

(Source: Network World Fusion) In its battle to get IPv6 widely deployed, the Internet engineering community is pursuing an infiltration strategy reminiscent of the Trojan War. http://www.idg.net/go.cgi?id=186618 Now this is novel and I would not have brought it to anyones attention except this is the 5th time in the last 3 days this issue has come up. -- Thank you; |---------------------------------------------------| | Thinking is a learned process so is UNIX | |---------------------------------------------------| Henry R. Linneweh

1 0

IOS 12.0.7S version
by Hyunseog Ryu/Brookfield/Norlight 16 Nov '99

16 Nov '99

Hi, folks Is there anybody use IOS 12.0(7)S version? We got PA-2T3+ card for Cisco 7507, and upgraded its software from 11.2P to 12.0(7)S. After that, suddenly routing didn't work. We use BGP for external connection and OSPF for internal connection. But traffic from OSPF didn't go to outer Internet at all. Is there any factors that I need to adjust? We tried to traceroute from internal network to Cisco 7507, and it was fine. When we tried to traceroute from Cisco 7507 to outer Internet, it was fine. But when we tried to traceroute from internnal network to outer Internet, there was timeout at Cisco 7507. When I use "sh ip route", it looks fine. I don't know why. Please let me know the reason or solution. Thanks in advance. Hyun ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Hyunseog Ryu Network Engineer/Applications Engineering Norlight Telecommunications, Inc. 275 North Corporate Drive Brookfield, WI 53045-5818 Tel. +1.262.792.7965 Fax. +1.262.792.7733

4 4

Re: Visual traceroute tools
by Jesper Skriver 16 Nov '99

16 Nov '99

On Mon, Nov 15, 1999 at 10:59:00PM +0000, Chris Horry wrote: > On Mon, 15 Nov 1999, Andrew Brown wrote: > > > > > >> http://www.visualroute.com looks fairly cool to me. > > > > > >But it doesn't seem to use rfc1712 or rfc1876 > > > > i can't say for sure, but i think it just guesses based on the owner > > of the address block. > > Guesses on owner of address block, whois records, LOC records, its own > database and if all else fails, the TLD. It reports unknown locations > to the master server as well, which is nice. Very good piece of software > :-) Just been in contact with them, and they currently does not support rfc1876 LOC records. /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.

1 0

TrACESroute 6.0 release
by Ehud Gavron 16 Nov '99

16 Nov '99

Announcing the All New TrACESroute 6.0 GOLD! At the suggestion of several nanog readers, my traceroute 2.9.4 has been renumbered to The All New TrACESroute 6.0 GOLD. Note that this is a higher revision level than either Netscape 4.8, IE5, or AOL 5, and is therefore the clearly superior software.* New features: 1. Parallel packets allow instant O(1) traceroutes! -P Out of beta and into production 2. Allow unnatural masks for full CIDR compatibility. (-DFORCE_NATURAL_MASK overrides) 3. Various bugfixes, segfault fixes, FreeBSD fixes, bounds checks, * In the United Kingdom, please consider this superiour software. the file: ftp://ftp.aces.com/pub/software/traceroute/traceroute.c the readme: ftp://ftp.aces.com/pub/software/traceroute/0_readme.txt the faq: ftp://ftp.aces.com/pub/software/traceroute/faq.txt Ehud Gavron, Technical Director RMI.NET Southwest Region Affiliation for identification purposes only

1 0

SprintNAP
by Simon Lockhart 16 Nov '99

16 Nov '99

Does anyone have a URL for SprintNAP? I can't seem to find anything through my usual bookmarks, and a search for "sprintnap" on sprint's site doesn't find anything. I'm after some basic information at the moment - Location, Description, Joining Info, Who's there... Thanks, Simon -- Simon Lockhart | Tel: 01737 839676 Senior R&D Engineer, Online | Fax: 01737 839665 BBC Research & Development | Email: Simon.Lockhart(a)rd.bbc.co.uk Kingswood Warren, Tadworth, Surrey. | URL: http://www.bbc.co.uk/rd/

2 1

Re: Visual traceroute tools
by Dennis Simpson 15 Nov '99

15 Nov '99

>>Any visual traceroute or similar applications using this ? http://www.visualroute.com looks fairly cool to me. Thx, dennis /-------------------------------------------------------------------\ | Dennis Simpson, President dennis(a)bconnex.net 705-725-0819 | | Barrie Connex Inc. High Performance Internet Engineering | | Central Ontario, Canada For When It Matters | \-------------------------------------------------------------------/

3 3