Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: jjb@zeus.cs.wayne.edu (Jon J. Brewster)
Newsgroups: comp.sys.sun
Subject: Re: OS 4.0, YP, and named
Message-ID: <8901191517.AA02095@zeus.cs.wayne.edu>
Date: 26 Jan 89 08:51:29 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 38
Approved: Sun-Spots@rice.edu
Original-Date: Thu, 19 Jan 89 10:17:44 EST
X-Sun-Spots-Digest: Volume 7, Issue 122, message 8 of 11
X-Issue-Reference: v7n111

In v7n111, sysrick@cfht.cfht.hawaii.edu writes:
>nameserver as per the Sun instructions and have restarted ypserv as ypserv
>-i.  I have also create /etc/resolve.conf with our internet domain in it
>and the internet address of the name server (our internet and YP domains
>differ)

Ypserv -i is not supported under V4.0.  And, the manual does not imply
that it will talk to named.  There is a different ypserv, distributed with
the nameserver kit which does talk to named.  There is no way I know of to
make the ypserv which was distributed with 4.0 work with named.  You
simply install the other ypserv.

>Tests using nslookup are fine except that nslookup starts up thinking our
>internet domain == YP domain.

This is what our system does:
ares# /bin/domainname
foo
ares# cat /etc/resolv.conf
nameserver 35.194.242.2
domain frobazzle
ares# nslookup
Default Server:  ZEUS.cs.wayne.edu
Address:  35.194.242.2

> set all
Default Server:  ZEUS.cs.wayne.edu
Address:  35.194.242.2

Set options:
  nodebug         defname         search          recurse         novc
  querytype=A     class=IN        timeout=6       retry=4
  domain=frobazzle
  search list: frobazzle 
  root=sri-nic.arpa

Note that the domain is the one listed in /etc/resolv.conf, not the one
returned by /bin/domainname.  (Which is what ypserv uses).