Identify process sending ldap requests to old DNS server
Hi,
I have a Solaris 10 system, which appears to be sending out LDAP queries to a server that is due to be decomissioned.
Is there a way to identify which process is sending out these queries? The problem is that the local port constantly changes, and the connections do not stay open long enough to query them using netstat or lsof.
I can see the outbound traffic in snoop:
and also in netstat:
But cant think of a way to identify what process is sending this out. I've checked resolv.conf & /etc/nsswitch.conf and the decom server is not listed anywhere.
I have no idea where the information for this decomServer is coming from, or which process is sending. Is there a way I can find this out?
I have just started learning Unix on Solaris and have been asked to learn DHCP, DNS and LDAP very quick in order to implement them and maintain.
Does anyone know how to do this or a decent book that will include all the above three which tells you how to install and maintain. All i have found so... (2 Replies)
Hi all
Is there any reason to have "hosts ldap dns" as line in /etc/nsswitch.conf ? My understanding is that ldap does not contain any host information..(?)
Best regards...Ludwig (1 Reply)
Dear guys,
I am facing the most weird problem I have ever encountered!
Ok here is the situation:
From my dns query.log file - it is generated using usual bind9 logging:
logging {
channel query.log {
file "/var/log/bind9/query.log" versions 10 size 2m;
severity debug 2;... (0 Replies)
Hi everybody,
Is it possible to have a URL link i.e. <a href=""></a>, which sends out two requests to a site?
As an example, I want want to combine these two links. The first link loads files. The second link searches these files. But I want just one link, where went a user clicks on it,... (3 Replies)
My environmnet : solaris 10 u 7 sparc
To configure DNS bind use Ldap as zone record database, I use bind 9.7.0 and sun directory 5.2
I do follow http://imil.net/docs/Configuring_DNS_zones_with_LDAP.txt
and stuck at make install
Error from bind log "database: error: unsupported database... (0 Replies)
I'd like to get some opnions on choosing DNS server:
Windows DNS vs Linux BIND comparrsion:
1) managment, easy of use
2) Security
3) features
4) peformance
5) ??
I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
hi
I am seeking to create a cgi-bin type creation that will allow users browsing the site to be able to run searches that would be a grep command or SED in the backround. I am not sure how to go about this, if you would give me a pointer or direction about what technology i could inform myself... (0 Replies)
I have very limited knowledge on LDAP configuration and have been trying fix one issue, but unsuccessful.
The server, I am working on, is Solaris-10 zone. sudoers is configured on LDAP (its not on local server). I have access to login directly on server with root, but somehow sudo is not working... (9 Replies)
Discussion started by: solaris_1977
9 Replies
LEARN ABOUT REDHAT
ldap_open
LDAP_OPEN(3) Library Functions Manual LDAP_OPEN(3)NAME
ldap_init, ldap_open - Initialize the LDAP library and open a connection to an LDAP server
SYNOPSIS
#include <ldap.h>
LDAP *ldap_open(host, port)
char *host;
int port;
LDAP *ldap_init(host, port)
char *host;
int port;
DESCRIPTION
ldap_open() opens a connection to an LDAP server and allocates an LDAP structure which is used to identify the connection and to maintain
per-connection information. ldap_init() allocates an LDAP structure but does not open an initial connection. One of these two routines
must be called before any operations are attempted.
ldap_open() takes host, the hostname on which the LDAP server is running, and port, the port number to which to connect. If the default
IANA-assigned port of 389 is desired, LDAP_PORT should be specified for port. The host parameter may contain a blank-separated list of
hosts to try to connect to, and each host may optionally by of the form host:port. If present, the :port overrides the port parameter to
ldap_open(). Upon successfully making a connection to an LDAP server, ldap_open() returns a pointer to an LDAP structure (defined below),
which should be passed to subsequent calls to ldap_bind(), ldap_search(), etc. Certain fields in the LDAP structure can be set to indicate
size limit, time limit, and how aliases are handled during operations. See <ldap.h> for more details.
typedef struct ldap {
/* ... other stuff you should not mess with ... */
char ld_lberoptions;
int ld_deref;
#define LDAP_DEREF_NEVER 0
#define LDAP_DEREF_SEARCHING 1
#define LDAP_DEREF_FINDING 2
#define LDAP_DEREF_ALWAYS 3
int ld_timelimit;
int ld_sizelimit;
#define LDAP_NO_LIMIT 0
int ld_errno;
char *ld_error;
char *ld_matched;
int ld_refhoplimit;
unsigned long ld_options;
#define LDAP_OPT_REFERRALS 0x00000002 /* set by default */
#define LDAP_OPT_RESTART 0x00000004
/* ... other stuff you should not mess with ... */
} LDAP;
ldap_init() acts just like ldap_open(), but does not open a connection to the LDAP server. The actual connection open will occur when the
first operation is attempted. At this time, ldap_init() is preferred. ldap_open() will be depreciated in a later release.
ERRORS
If an error occurs, these routines will return NULL and errno should be set appropriately.
OPTIONS
Options that affect a particular LDAP instance may be set by modifying the ld_options field in the LDAP structure. This field is set to
LDAP_OPT_REFERRALS in ldap_open() and ldap_init(), which causes the library to automatically follow referrals to other servers that may be
returned in response to an LDAP operation.
The other supported option is LDAP_OPT_RESTART, which if set will cause the LDAP library to restart the select(2) system call when it is
interrupted by the system (i.e., errno is set to EINTR). This option is not supported on the Macintosh and under MS-DOS.
An option can be turned off by clearing the appropriate bit in the ld_options field.
NOTES
There are other elements in the LDAP structure that you should not change. You should not make any assumptions about the order of elements
in the LDAP structure.
SEE ALSO ldap(3), ldap_bind(3), errno(3)ACKNOWLEDGEMENTS
OpenLDAP is developed and maintained by The OpenLDAP Project (http://www.openldap.org/). OpenLDAP is derived from University of Michigan
LDAP 3.3 Release.
OpenLDAP 2.0.27-Release 22 September 1998 LDAP_OPEN(3)