sysrick@cfht.cfht.hawaii.edu (01/19/89)
We are trying to start up a domain name server with little luck. We have been running YP fine under 4.0 for about 6 months. I have setup a 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) Tests using nslookup are fine except that nslookup starts up thinking our internet domain == YP domain. The problem comes when a telnet or ftp tries to access a host name not in YP hosts -- get "unknown hostname xxxxx" even though nslookup can find it. One question (among many) is -- what triggers the host lookup to go from YP to using the name server ? Rick McGonegal INTERNET sysrick@cfht.hawaii.edu C.F.H.T. Corp. PO Box 1597 Kamuela Hawaii 96743 FAX (808) 885-7288 (808) 885-7944 TELEX 633147 CFHT
peters@cc.msstate.edu (Frank W. Peters) (01/26/89)
Sun Yellow Pages as released with 4.0 (I have no experience with 3.x
versions) has two problems with using the Domain Name System.
First, it won't work. :-) The following is a quote from the README
included with the fix:
Problem description:
YP link to resolver for name resolution does not seem to work.
Little documentation exists to support this setup. The
makedbm -b option is supposedly necessary for interdomain
name lookup. The makedbm -b option does add a YP_INTERDOMAIN
key to the hosts map however interdomian host resolution still
fails under YP.
Also, due to an uninitialized variable, programs that are linked static
(such as mount) that do YP host name lookups can hang if the ypserv
is using the inter-domain resolver (ypserv -i in 3.x or makedbm -b
in 4.x).
Fix description:
A problem exists with the case respresentation for the string
"YP_INTERDOMAIN" within ypserv which causes ypserv not to
recognize the host map interdomain key reference built by
makedbm for the name service resolver link. This a fixed
68020 version ypserv only for use on a Sun3 running SunOS 4.0.
Also fixes obscure bug that caused mounts to hang, and local names
to hang when the name server was down.
Also note that another problem exists related to ypxfr
transfer of yp master host map data to slave servers
resulting in the slave server unable to serve as a resolver
link. This is a fixed 68020 ypxfr version which will
allow Sun3 4.0 yp slave servers to receive correctly built
host map data from a 4.0 yp master server and link with
the resolver as a slave server.
The fix to this problem is included with 4.0.1
The second problem is only relevant to suns acting as both a nameserver
and YP master. This symptoms are that if the link to the root name servers
is broken (say a gateway crashes) the server will begin to send repeated
packets to all of the root servers until it gets a response. It sends
these packets JUST AS FAST AS IT CAN with NO pauses. Our gateway used to
be one of the small 68000 based proteons and it couldn't keep up (which
meant our link would crash which meant the root servers were definitely
not reachable which meant the server kept banging which crashed the
gateway as it rebooted... and so forth). As if this weren't bad enough,
while all of this is going on the server will not be able to resolve names
IN ITS OWN YP MAPS OR DNS DATABASE. This means that you can't rlogin or
telnet to the server or any of its clients and cannot nfs mount
filesystems (see the end of the first paragraph under 'fix description'
above). Any filesystems already mounted seem to be fine.
Sun also has fixes for this problem (by changes to the same executables as
above). THESE FIXES ARE NOT INCLUDED IN 4.0.1.
Hope this information helps. Drop me a note if you have any questions.
Frank Peters
Internet: peters@CC.MsState.Edu
BITNET: PETERS@MSSTATE.BITNETjjb@zeus.cs.wayne.edu (Jon J. Brewster) (01/26/89)
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).
stan%prism@gatech.edu (Stan Corbin) (01/31/89)
In article <204@uwila.cfht.hawaii.edu> sysrick@cfht.cfht.hawaii.edu writes: >We are trying to start up a domain name server with little luck. We have >been running YP fine under 4.0 for about 6 months. I have setup a >nameserver as per the Sun instructions and have restarted ypserv as ypserv >-i. >One question (among many) is -- what triggers the host lookup to go from >YP to using the name server ? I think that as of 4.0, use of the name server is not triggered by "-i" on ypserv, but rather by adding "-b" to the makedbm for the hosts map. Also, there is at least one patch to ypserv that you might need to make it work (sorry, I don't have the number handy, but I think it was pretty popular, so Sun should know what you need). [[ See volume 7 number 122 (sent last Wednesday). --wnl ]] -- Stan Corbin stan@prism.gatech.edu Office of Computing Services ...!gatech!prism!stan Georgia Institute of Technology Atlanta, Georgia 30332-0275