BIND/NIS server problem

From: David C. Tuttle <dct_at_odin.mda.uth.tmc.edu>
Date: Wed, 23 Aug 1995 14:56:25 -0500 (CDT)

I am encountering a BIND problem with my AlphaServer 2100 Model 5/250
running Digital UNIX v3.2B. I have configured it to be an NIS slave
server and BIND client. This works OK locally -- "nslookup" works,
and all hostnames are resolved (local, YP, and BIND all work).

However, when *other* hosts on my network use the Alpha as their NIS
server and use a hostname not in the NIS maps, it comes back "Host
unknown". When I "ypset" to another NIS server (one of two SunOS v4.x
machines), the problem goes away, and when I "ypset" back, the problem
comes back.

Apparently, NIS and BIND are not cooperating on the Alpha. I have
rerun "nissetup" and "bindsetup" and even "svcsetup", which tells me
that the lookup order for hostnames is "local,bind,yp". The Alpha
uses the same nameservers in the same order as my other machines,
which don't exhibit this problem. This should work, shouldn't it?

I'd appreciate hearing from anyone with information on this. Thanks.

-- 
David C. Tuttle, Biomathematics   ----> dct_at_odin.mda.uth.tmc.edu <----
The University of Texas M.D. Anderson Cancer Center    +1 713 792 2606
Mail Stop 237, 1515 Holcombe Boulevard, Houston, TX  77030-4096    USA
Today's anagram of "David Charles Tuttle" is:  THUD AT DRASTIC LEVEL
Received on Wed Aug 23 1995 - 22:15:42 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:45 NZDT