SUMMARY: DNS & resolver problems

From: Derek Terveer (
Date: Mon Sep 19 1994 - 16:15:09 CDT

Originally I wrote about the problem i was having getting DNS to work
on one of my class c networks. Getting DNS to work on the suns is
pretty simple; add the -b to the NIS makefile and set up the
/etc/resolv.conf file. And this worked just fine on every network
except one. I don't know if this fixes any larger, underlying problem,
but I finally got that rogue network to talk to the internet by
starting up ypserv with the -d option on its NIS server (slave). (-d
means use DNS, if needed) the other NIS servers (master or slave) on
the other networks don't have ypserv running with the -d option, so i
don't know why it should be any different.

Some of the various suggestions were as follows:

verify /etc/defaultrouter is correctly set up
turn off in.named
use direct DNS lookup, bypassing NIS (2)
no default route specified in routing tables (2)
make sure -b cookie is present in hosts NIS map (2)
reinitialize NIS master (ypinit -m)

thanks to all the responders! (including the following:) (Michael G. Harrington)
Larry Chin <> (Joe Turner) (David Weitzel)
rauthenberg@HHI.DE (Stefan Rauthenberg)
grevemes@VTC.TACOM.Army.Mil (Steven Grevemeyer)

original question:

> I have three class C nets: 199.86.16, ..17, ..18 and a mix of solaris 1.1.1
> and solaris 2 machines. the DNS primary is running solaris 1.1.1. i have
> the -b flag enabled on the NIS server. the problem is that i can successfully
> perform nslookups on all three networks, but pings and applications like gopher
> only work on two of the networks (16 and 18). The 199.86.17 network has its
> own NIS slave, just like each of the other nets, with a resolv.conf file and,
> now, also its own in.named ruuning too.
> The FMs only state that all that is required to have NIS+DNS lookup of host
> names is to create the resolv.conf file. pretty simple, and this works
> on all of the networks except that one.
> what am i doing wrong?? this is starting to get really frustrating.
> here is what the /etc/resolv.conf file looks like on the 17 network (same as
> on the other nets):
> domain
> nameserver
> nameserver
> nameserver
> is our DNS primary. here is what happens on a typical 17 host:
> pothole:derekt$ ypwhich
> pothole:derekt$ ping
> ping: unknown host
> pothole:derekt$ nslookup
> Server:
> Address:
> Name:
> Address:
> how can i get it to use DNS with ping, etc?

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:10 CDT