DNS and SAM -- oh why can't they play together

[Joe Bozen]

Ok, now this is weird (for me)

When I try to ping www.yahoo.com I get timeout errors. Ok, well, I decided to setup DNS. Once I modify my /etc/resolv.conf file to add:

doman stfrancis.edu
nameserver 10.0.0.38

I can then ping www.yahoo.com however, SAM stops working as well as some of the applications on my CDE.

My guess is that I'm probally missed some file in my setup routine.

Any ideas?

SAM-less

[Michael Tully · Accepted solution]

Have a look at the /etc/nsswitch.conf files.
There are a few to choose from in /etc/nsswitch.*

I always use this combination, but my server is inside a firewall. You may have to fiddle with it (them)

hosts: files [NOTFOUND=continue UNAVAIL=return TRYAGAIN=return] dns [NOTFO
UND=return UNAVAIL=continue TRYAGAIN=return]

[Joe Bozen]

That worked.

I ran SAM's Name Service Switch and modified the hosts parameter. Doing so created a nsswitch.conf. This file now reads:

hosts: files [NOTFOUND=continue UNAVAIL=continue] dns

DNS and SAM are now living together in peace and harmony.

Thanks again.

joe...

[Steven E. Protter]

The next quote is meant in fun....

Real Sysadmins don't use gui's

Bill Hassell

Sam is good at some things, and not good at others. I never, not matter how sleepy I am use it for certain tasks for example the one you are trying to get done. I also never use it for network changes because for reasons I don't know sometimes it puts duplicate entries in netconf.

Right tool for the right job. Its good you had to do this the Sam-less way.

Its nice that I can attribute my quotes to someone else.

As an admin, I use sam very seldom. I make it my goal to learn how to do things the command line way. Why? Because there is no sam in single user mode.

Glad your issue is resolved. No points required, just on the old soapbox.

SEP

[Bill Hassell]

You're probably wondering why this change makes your system work again. When you specify a DNS server, the default is to look at DNS only, or to follow the nsswitch.conf rules. Your DNS server 10.0.0.38 has no information about your computer and that breaks a *lot* more things than just SAM. Your DNS server probably never heard of localhost either, both very important in networking. By specifying files...dns in the nsswitch.conf file, all network lookups will start with /etc/hosts and if not found, go to your DNS server. That's the best way to arrange nsswitch.conf.

[Joe Bozen]

Real admins, huh????

The only thing real about me is my confusion :) I'm new to HPUX, I was a VMSadmin then a TRU64admin and now I'm working on HPUX and this has been for about 4 weeks. I hope to in time to have a better understanding of HPUX, but from what I've seen for far, I think the best thing about HPUX is this users group. My hat goes off to all of those out there that take their time to assist others.

I hope to become less reliant on SAM but it has really helped me go from 0 to 60 in a short period of time. I am the only UNIX person here and this accounts for about 1/20 of my overall responsibilities. Jack of all trades, master of none...

joe...

[Thomas Bianco]

I'm sorry; I saw the quote and had to chime in, completely off topic.

I have a bumper sticker on my desk back at my parents house (I had it when I was 12, cut me some slack) that reads "real men do it from the dos prompt".

I got it just about the time my father got fed up with c:\config.sys and installed windows on my 286. I was so angry he had thrown such unneeded graphical nonsense on my finely tuned QEMM machine that I rode my bike (i was 12, remember) down to the computer store and plopped down my allowance and stuck it to the desk right under the keyboard.

I think he took the point and went out and purchased a new 386 for himself and left the 286 to me.

Ok, zero points for this self indulgent off topic nonsense.