|
Home > Archive > Unix True 64 > March 2004 > Nameserver Query to internet...
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Nameserver Query to internet...
|
|
|
| Is anyone aware of a default setting someplace in Tru64 4.0x that would
affect machines starting up the dtlogin (xauth, etc) due to requiring what
appears to be a DNS query to the internet? We have an internal dns,
nis(yp services), nfs and so on. Recently we lost internet for over
24hours and it appears as the cache TTLs died off our tru64 and solaris
stations began to be unable to start the dtlogin dropping us to the
console. This is not happening on Linux or IRIX. I have been rumaging
through packets just outside our lan as well as packets I pulled off a
mirrored port of one of the tru64 stations but so far I have had little
luck in finding the specific query thats occuring.
Appreciate any input someone has.
TIA.
| |
|
| On Tue, 09 Mar 2004 07:36:26 +0000, jason wrote:
> Is anyone aware of a default setting someplace in Tru64 4.0x that would
> affect machines starting up the dtlogin (xauth, etc) due to requiring what
> appears to be a DNS query to the internet? We have an internal dns,
> nis(yp services), nfs and so on. Recently we lost internet for over
> 24hours and it appears as the cache TTLs died off our tru64 and solaris
> stations began to be unable to start the dtlogin dropping us to the
> console. This is not happening on Linux or IRIX. I have been rumaging
> through packets just outside our lan as well as packets I pulled off a
> mirrored port of one of the tru64 stations but so far I have had little
> luck in finding the specific query thats occuring.
>
> Appreciate any input someone has.
>
> TIA.
What I have noticed is this. If I unplug the network from a machine
dtlogin+xdm will fail as noted below. The odd thing is if I watch this
same machine with the network plugged in a see not one packet leaving it
on boot. I suppose somehow I could be missing the packets but I am
watching for ether host (hardware/mac addy not IP or the like). What
would cause the error below that is network related just bringing up the
dtlogin at first boot? Worse, what would loss of internet connectivity
have to do with this when I cant find one reference to any outside source
on these machines. The closest they come to anything outside the lan is
their primary and secondary nameservers are internal caching NS'.
xdm error (pid 674): Hung in XOpenDisplay(:0), aborting
xdm error (pid 674): server open failed for :0, giving up
xdm error (pid 670): Display :0 cannot be opened
Thanks.
|
|
|
|
|