The solution to my grief was to run ypbind -ypsetme before trying
ypset jts. BTW, jts, once bound, responds properly to NIS/DNS requests.
Thanks to:
Ricky Marek (ricky@fibronics.co.il)
Claus Assmann (ca@informatik.uni-kiel.de)
Original message:
> We recently changed over our NIS domain from jts to jts.com and added
> DNS in preparation for our direct Internet connection. Gory details:
>
> NIS master: jts
> NIS slave: mustang
> DNS primary: jts
> DNS secondary: mustang
> OS (on both): SunOS 4.1.2
>
> As per the ypserv man page, we're now running "ypserv -d".
>
> As per /var/yp/Makefile, we changed "B=" to "B=-b".
>
> Symptoms:
>
> 1. It would now seem that no host can bind to jts. Everybody is
> bound to mustang.
>
> 2. nslookup can successfully retrieve DNS data from jts. Ditto for mustang.
>
> 3. ypset on a client (e.g., lemon) seems to get rejected, e.g.,
>
> # ypset jts
> ypset: Sorry, ypbind on host lemon has rejected your request.
>
> Any ideas?
>
> As usual, will summarize.
-- Jim Carroll | JTS Computer Systems Ltd. | Seasons Greetings - Beware of jimc@jts.com | Toronto, Ontario | low-flying Clauses.... :-)
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:31 CDT