01-24-2014
If I understand you correctly, clients experience a very long delay connecting to the Solaris box. So the fact that the Solaris doesn't use DNS is surely irrelevant. Question is what is the DNS setup of the clients.
What you describe has all the hallmarks of a DNS issue ie, name resolution delays (or possibly mis-routing on the network).
What if you telnet from a client giving the Solaris ip address instead of nodename?
What is the DNS environment that the clients are in????
Last edited by hicksd8; 01-24-2014 at 08:25 AM..
4 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
1 . Thanks everyone who read the post first.
2 . I have a log file which size is 143M , I can not use vi open it .I can not use xedit open it too.
How to view it ?
If I want to view 200-300 ,how can I implement it
3 . Thanks (3 Replies)
Discussion started by: chenhao_no1
3 Replies
2. UNIX for Dummies Questions & Answers
I have a 5000 line config.log file with several "maybe" errors. Any reccomendations on finding solvable problems? (2 Replies)
Discussion started by: NeedLotsofHelp
2 Replies
3. Shell Programming and Scripting
How to repeat the execution of a simple command like the following for 1 sec ?
echo Hi
The completion time for the command is not known, but we need to calculate the number of times this commans executes successfully within 1 sec.
Thanks
Kumarjit (5 Replies)
Discussion started by: kumarjt
5 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I got following problem I want to use encrypted password and login for my script for oracle DB.
#This was created with echo "login" | openssl enc -base64 and echo "password" | openssl enc -base64
login= bG9naW4K
passwd= cGFzc3dvcmQK
Im using following... (4 Replies)
Discussion started by: kvok
4 Replies
LEARN ABOUT MOJAVE
dnsextd
dnsextd(8) BSD System Manager's Manual dnsextd(8)
NAME
dnsextd -- BIND Extension Daemon
SYNOPSIS
dnsextd
DESCRIPTION
dnsextd is a daemon invoked at boot time, running alongside BIND 9, to implement two EDNS0 extensions to the standard DNS protocol.
dnsextd allows clients to perform DNS Updates with an attached lease lifetime, so that if the client crashes or is disconnected from the net-
work, its address records will be automatically deleted after the lease expires.
dnsextd allows clients to perform long-lived queries. Instead of rapidly polling the server to discover when information changes, long-lived
queries enable a client to indicate its interest in some set of data, and then be notified asynchronously by the server whenever any of that
data changes.
dnsextd has no user-specifiable command-line argument, and users should not run dnsextd manually.
SEE ALSO
mDNS(1) mDNSResponder(8)
For information on Dynamic DNS Update, see RFC 2136 "Dynamic Updates in the Domain Name System (DNS UPDATE)"
For information on Dynamic DNS Update Leases, see http://files.dns-sd.org/draft-dns-update-leases.txt
For information on Long-Lived Queries, see http://files.dns-sd.org/draft-dns-llq.txt
BUGS
dnsextd bugs are tracked in Apple Radar component "mDNSResponder".
HISTORY
The dnsextd daemon first appeared in Mac OS X 10.4 (Tiger).
Darwin June 1, 2019 Darwin