strange resolver behavior on Solaris 8 client

[Peter Dambier]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Bob,

I may be wrong but on Solaris if DNS behaves peculiar then the reason
very often is NIS.

bob_a_booie wrote:
| Here is my situation  :
| I have 2 solaris hosts running same version of solaris 8
| and identical /etc/resolv.conf and and on the same phsyical network and
| subnet. Both are V120
|
| Why would Solaris hosts with identical resolver settings
| on the same network behave differently ?

How about /etc/nsswitch.conf

hosts: files dns nisplus nis

|
| Host serverb will take at least 15 minutes for any dynamic updates
| to resolve correctly via ping or nslookup.
|
| Host servera will take no more then 2 minutes for any dynamic updates
| to resolve correctly via ping or nslookup.
|
|
| Are there any particular environment settings
| that can cause this ?
|
| Unfortunatley serverb is a centralized  location for rsyncing
| data and distributing software ...

Then very likely its /etc/nsswitch will look like

hosts:  nisplus nis files dns

It will look into NIS first. Maybe NIS does name caching - for
/etc/hosts or its equivalent tables it does.

|
| TIA
|
|

Regards,
Peter and Karin Dambier

- --
Peter and Karin Dambier
Public-Root
Graeffstrasse 14
D-64646 Heppenheim
+49-6252-671788 (Telekom)
+49-6252-599091 (O2 Genion)
+1-360-226-6583-9738 (INAIC)
mail: peter at peter-dambier.de
http://iason.site.voila.fr
http://www.kokoom.com/iason
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQFCtv5jPGG/Vycj6zYRAgG4AJ9DUARPTYNnK3C7MOVJi2ZMIXw1RACfTDah
OoAXS97q2kZEhORKelu03Kg=
=MmFg
-----END PGP SIGNATURE-----