jordan@ucbvax.ARPA (Jordan Hayes) (08/03/85)
In article <550@down.FUN> honey@down.FUN (Peter Honeyman) says again: >jordan states that a host may be a member of more than one domain. >possibly he is referring to the following passage from rfc819: > [ see references to rfc819 and 920 ] > ...changed its name. This means that any previous references to > USC-ISIA.ARPA are now out of date. > >it appears to me that the issue was resolved in favor of domain uniqueness. Oh, Peter. It has changed its name in the internet namespace. This says nothing of any references in the UUCP namespace it may have. It seems pretty important for there ti be a pseudo-domain UUCP due to the problems of registering directly with the NIC (you mentioned money, of course...). Listen, of course we don't have the resources to provide the "real" domaining system as being implemented by the internet, but we can at least fake it well. What *is* a nameserver, but just an authority on how to get from a to b, right? why can't simpleton sites on UUCP just use a database for this? Just know enough to make things work correctly? The table it uses could be as smart as you'd like it to be, or as limited. However, if you resolved everything for .ATL.UUCP to host FOO, and then you said, well, I'd also like to forward everything for PRINCETON.ATL.UUCP to FOO and also DOWN.PRINC... I'd like to think that you'd get tired fingers from typing, and assume that everything below it goes to FOO as well. The passage you quote references "nicnames", I believe, not really multiple parentage hosts. ------------ Jordan Hayes jordan@UCB-VAX.BERKELEY.EDU UC Berkeley ucbvax!jordan +1 (415) 835-8767 37' 52.29" N 122' 15.41" W