As an aside from comp.sys.sgi.admin:
On Thu, 08 Jul 1999 03:59:43 GMT, [email protected] wrote:
>Hi all,
>
>We have an SGI Octane running 6.5.4. As a client, I cannot seem to
>get it to resolve names on our Internet providers DNS server (ie.
>Netscape cannot do a DNS lookup). I can ping the DNS servers using
>their IP address, so I know I can get out onto the net through our
>gateway and pass packets using IP addresses, but no name services. I
>know the name servers are functioning properly. I use same servers
>successfully for other platforms. I have the name servers listed in
>the resolv.conf file, network is on, and a good static route to our
>gateway. Any other files involved in name resolution??
Yes, /etc/nsswitch.conf. Make the "hosts" entry say:
hosts: files dns
...unless you are using nis.
You also need to do "nsadmin restart" or reboot after making modifications
to nsswitch.conf or resolv.conf.
Michael/font>
The Apache 1.3.6 webserver that the CCP14 uses should now be happy,
even if you are browsing via network links with
Lame or Misconfigured DNS servers. It looks like the cause of
the erratic Apache problem was compiling up Apache 1.3.6
using a GCC compiler inheritted from a previous version of
the IRIX operating system on the SGI O2 server. Thanks for
Drazen Kacar (E-mail: [email protected]) for helping to confirm this.
"If I decoded this correctly, you want to say that you have gcc compiled
on old version of IRIX. This is bad. Very bad. Gcc wants to have its
own include files and some of them depend on the things you got with
the OS. In general, when you use gcc compiled on a previous version
of any OS, weird things can happen. Since everything's OK with wget
produced with a native C compiler, I suppose weirdness you've
discovered can be attributed to the improper gcc setup."
Note of April 1999 - changing compilers does not seem to help things.
Note of ~20th April 1999 - Turn off DNS Hostname lookup to avoid the DNS problem
Note of ~1st May 1999 - The "/usr/local/apache/bin/logresolve" program seems to hang
trying to resolve IP addresses to names - thus may have something reproduceable to work with later.
Note of 6th May 1999 - Re problem with DNS lookup and Lame DNS servers with Apache 1.3.6
Based on a post on comp.sys.sgi.apps (Title: Re: Ping #'s not names?) reconfigure the "nsd" - UNS name
service deamon which might fix the problem due to the default installation not having the required
option in the nsswitch.conf. (I think the reboot means "chkconfig restart"). Try testing using the
Apache "logresolve" program.
Newsgroups: comp.sys.sgi.apps
Subject: Re: Ping #'s not names?
Date: Thu, 6 May 1999 21:47:13 LOCAL
In article Ralf Beyer writes:
> From: Mark Snyder
> Hi all,
>
> I have a problem with my name server. I can use nslookup to get the dns
> #, but Navigator nor Ping nor traceroute will "resolve" "unknown host".
> Any ideas on what might be causing this? Where can I look next to try
> and get it to work properly.
> Thanks,
> Mark
>
>You don't say what OS you have.
>For IRIX 6.5.2 and later:
>man nsd
>su
>Check /etc/nsswitch.conf that it contains
>the line
> hosts: nis dns files
>
>chkconfig nsd on
>reboot
>Regards
>[email protected]
>German Aerospace Center (DLR)
>Deutsches Zentrum fuer Luft- und Raumfahrt e.V.
Note of 6th May 1999 - and a bit - Problem still occuring. Logresolve gets stuck on:
206.31.39.208 - - [27/Mar/1999:21:06:41 +0000] "GET /ftp-mirror/alife/alifegame/pub/alife-game/program
/sounds/ HTTP/1.1" 200 830
206.31.39.208 - - [27/Mar/1999:21:06:41 +0000] "GET /icons/blank.gif HTTP/1.1" 200 148
206.31.39.208 - - [27/Mar/1999:21:06:42 +0000] "GET /icons/back.gif HTTP/1.1" 200 216
206.31.39.208 - - [27/Mar/1999:21:06:42 +0000] "GET /icons/binary.gif HTTP/1.1" 200 246
sv1% nslookup 206.31.39.208
Server: nserv1.dl.ac.uk
Address: 148.79.80.78
*** nserv1.dl.ac.uk can't find 206.31.39.208: Non-existent host/domain