Henrik Carlqvist wrote:
> I don't do this NIS-server-thing very often (it was a few years since the
> last time), but I will try to help anyway.
>
> Mark Johnson <mXrXj001@shaw.ca> wrote:
>
>>I followed the directions in the NIS HOWTO, but I get the following
>>error on the server:
>>mj@enterprise:~/seti$ ypwhich -m
>>Can't get map list for domain enterprise. Reason: Can't bind to server
>>which serves this domain
>
>
> On the server you should be running both ypserv and ypbind. Did you also
> start ypbind?
>
>
>>If I run ypserv with the -d option, it prints out this:
>>root@enterprise:/var/yp# ypserv -d
>>[ypserv (ypserv) 2.13]
>>
>>Find securenet: 255.0.0.0 255.0.0.0
>>Find securenet: 255.255.255.0 255.255.255.0 ypserv.conf:
>>192.168.1.0/192.168.1.0:*:*:0 ypproc_domain_nonack("enterprise.yp")
>>[From: 192.168.1.3:32781]
>> -> Ignored (not a valid domain)
>>
>>
>>I originally had "enterprise.yp" in my /etc/defaultdomain file, but
>>changed it to "enterprise" thinking that maybe it didn't like the name.
>
>
> If I remember right defaultdoamin is for ypbind but ypserv uses data from
> ypserv.conf. Maybe your ypserv.conf says something about "enterprise.yp"?
>
> regards Henrik
Starting ypbind on the server did not help.

I removed the "enterprise" directory from /var/yp, changed
/etc/defaultdomain to "johnson", and redid the "make" in this directory.
I still have the same error. In fact, it still prints the
"enterprise.yp" domain name in the error.

My ypserv.conf is as follows:
192.168.1.0/255.255.255.0:*:*:none
This is all I put in it, since none of the options described in the man
page seemed to need changing from their defaults.

I also updated yp.conf to tell it where to look for the server for the
"johnson" domain. This did not help.

I have noticed that I must use a fully qualified domain name or else the
dig command fails to resolve names on my LAN, despite having a "domain"
entry in resolv.conf. Since I am now using FQDNs in my config files for
NIS, I believe this to be a separate issue.

Googling on "not a domain" and "ignored" has not been helpful either. I
only found a posting to a newsgroup by someone having the same problem
as me, and who did not get any answers.

Mark