Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: steve@umiacs.umd.edu
Newsgroups: comp.sys.sun
Subject: Nameserver problems (?) in SunOS 4.0.3
Keywords: Networks
Message-ID: <1988@brazos.Rice.edu>
Date: 6 Oct 89 11:59:23 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 28
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 155, message 4 of 7

The domain name searching you're seeing was done deliberately, and is (for
most people) a feature rather than a bug.  People with sources generally
hack the resolver library sources to turn off the RES_DEFNAMES and/or
RES_SEARCH flags in the _res structure in res_init.c, then recompile...
but you probably can't do that.

The searching goes only up to two domains away from the root.  (For us,
that means that we'll look for 'foo' in foo.cs.umd.edu and foo.umd.edu,
but not foo.edu.)  The one case where this is legimately a problem is when
the second-level domain is served not by something local, but by (say) the
root servers.  Many of the military domains (i.e., navy.mil) are set up
this way.

I suppose it would be nice to have a way to turn off searching and default
names on a system-wide basis.  I'd still like to see the searching be made
a bit more flexible in the BIND resolver, but it seems unlikely (for
moderately good reasons) that such a change will never be put in by
Berkeley.

About MX sendmails: I think there is a fixed one out on uunet, probably as
sendmail.mx.  You might (if you don't mind losing the Sun sendmail YP
support) just choose to grab a copy of sendmail 5.61 from
ucbarpa.berkeley.edu instead, and use that over the Sun sendmail.

	-Steve

Spoken: Steve Miller    Domain: steve@umiacs.umd.edu    UUCP: uunet!mimsy!steve
Phone: +1-301-454-1808  USPS: UMIACS, Univ. of Maryland, College Park, MD 20742