Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!stanford.edu!agate!ucbvax!dcs.leeds.ac.uk!jj From: jj@dcs.leeds.ac.uk (J Jackson) Newsgroups: comp.protocols.tcp-ip Subject: name handling in DNS resolvers Message-ID: <21400.9105161229@csunb0.dcs.leeds.ac.uk> Date: 16 May 91 12:29:39 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 32 In experimenting with DNS (before dropping use of hosts files), we came across differences in the way different software resolved names that users had provided. BIND (and derivations - most UN*Xes) build a search list of progressively wider domains to successively append to the user provided name. This gives a decent user interface where users only need to specify enough 'local' part of the name - not the full domainname of a service. However some implementations do not provide such user friendly procedures. e.g. FTP Inc's PC/TCP uses the algorithm that if the user supplied name contains a '.' (period) it is used "as-is" in the DNS resolution, otherwise a default domain is appended. (FTP Inc. support staff don't think there is any need for change.) Such 'simpler' (brain dead!) procedures may be ok in a site without much sub-domaining, but for large sites users are forced to use fully qualified domainnames for any service outside their local sub-domain. Have others found this, and if so are you satisfied with the position? I have found nothing specific in the Host Requirements or DNS RFC's. Surely we should expect a standard appraoch to this? ======================================================================= Jim Jackson Email : School of Computer Studies UK - JANET : jj@uk.ac.leeds.dcs Leeds University Internet : jj@dcs.leeds.ac.uk Leeds LS2 9JT UK Phone : +44 532 335451 ======================================================================= Opinions! What Opinions? I just wield the brush round here.