Xref: utzoo news.admin:4048 comp.mail.uucp:2316 Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!mattc From: mattc@ncr-sd.SanDiego.NCR.COM (Matt Costello) Newsgroups: news.admin,comp.mail.uucp Subject: Re: Too many map entries. Summary: Fixed in next release Keywords: ncr.com Message-ID: <355@ncr-sd.SanDiego.NCR.COM> Date: 22 Nov 88 07:24:20 GMT References: <2660@sultra.UUCP> Distribution: na Organization: NCR Corporation, Rancho Bernardo Lines: 37 In article <2660@sultra.UUCP> dtynan@sultra.UUCP (Der Tynan) writes: >OK, I run the following command; > > grep sandiego.ncr.com | wc -l > >And I get 57. Yes, that's 57 machines at NCR, which appear in the maps. The policy of listing all machines was instituted many years ago, before the advent of domain routers. At that time UC Berkeley was listing ~650(?) machines, and domain routers consisted of hand-crufted sendmail rules to route all host names beginning with "ucb" to ucbvax, etc. This is mostly useless now, so I've sent in an updated map entry for ncr-sd that does not list any local hosts. Thanks go to Der Tynan for catching this, as I'd not realized that we were still doing this. > Comments anyone? There are several reasons why some sites list many of their internal hosts. The biggest reason to list all your hosts is to reserve the host name. 1. Too many sites seem to think that any simple host name in a UUCP path must be host.UUCP as well. As long as agressive rerouters exist, having a local host with a well-known name is tantamount to email suicide. 2. Netnews has not yet been domainized in the return path. Until it is, what are my chances of recieving the USENET maps if my host name is rutgers.sandiego.ncr.com? 3. UUCP does not handle domain names. Ncr-sd has had to reject a UUCP link with at least one machine because of a host name conflict. -- Matt Costello (CSNET) +1 619 485 2926 uunet!ncrlnk!ncr-sd!mattc