Sponsored Content
Operating Systems Solaris Identify process sending ldap requests to old DNS server Post 302910792 by badoshi on Monday 28th of July 2014 07:32:14 AM
Old 07-28-2014
Thank you for the pointer. I've went down the dtrace path, and found a script that did exactly what i needed:

conntrack DTrace script: connections by process, user and port on Solaris/Opensolaris | Core Networks Techno Blog

produces real-time output like the following, where the last column is the destination:

Code:
      adclient 19607     0    global     45708        88  TCP 10.x.x.x
      adclient 19607     0    global     45707       389  TCP 10.x.x.x
      adclient 19607     0    global     45707       389  TCP 10.x.x.x

Thanks for your assistance, dtrace is something that I should learn how to use, it looks very handy!
 

9 More Discussions You Might Find Interesting

1. IP Networking

DHCP, DNS and LDAP

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)
Discussion started by: ollyparkhouse
2 Replies

2. Solaris

/etc/nsswitch.conf hosts ldap dns

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)
Discussion started by: ludwig
1 Replies

3. UNIX for Advanced & Expert Users

udp sockets of dns requests not showing anywhere...

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)
Discussion started by: angeloio
0 Replies

4. Web Development

Sending two requests from one link

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)
Discussion started by: z1dane
3 Replies

5. Solaris

How to Configure DNS bind 9 with Ldap back-end

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)
Discussion started by: tien86
0 Replies

6. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

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)
Discussion started by: honglus
2 Replies

7. Shell Programming and Scripting

Direction to create website to process grep and SED requests

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)
Discussion started by: cdc01
0 Replies

8. IP Networking

DNS requests through SSH/443

Anybody know how to force all DNS requests through port 443 or an SSH tunnel such as Putty in Ubuntu 10.4? (2 Replies)
Discussion started by: 3therk1ll
2 Replies

9. Solaris

LDAP Client not connecting to LDAP server

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
lwresd(1M)																lwresd(1M)

NAME
lwresd - lightweight resolver daemon SYNOPSIS
config-file] debuglevel] pid-file] ncpus] query-port] port] directory] user-id] DESCRIPTION
The daemon provides name lookup services for clients that use the BIND 9 lightweight resolver library. It is essentially a stripped-down, caching-only name server that answers queries using the BIND 9 lightweight resolver protocol rather than the DNS protocol. listens for resolver queries on a UDP port on the IPv4 loopback interface, 127.0.0.1. This means that can only be used by processes run- ning on the local machine. By default, UDP port number 921 is used for lightweight resolver requests and responses. Incoming lightweight resolver requests are decoded by which then resolves them using the DNS protocol. When the DNS lookup completes, encodes the answers from the name servers in the lightweight resolver format and returns them to the client that made the original request. If the configuration file contains any entries, sends recursive DNS queries to those servers. This is similar to the use of forwarders in a caching name server. If no entries are present, or if forwarding fails, resolves the queries autonomously starting at the root name servers, using a compiled-in list of root-server hints. Options Use config-file as the configuration file. The default is Set the debug level to debuglevel. Debugging traces from become more verbose as the debug level increases. Run in the foreground. Run in the foreground and force all logging to standard error. Write the daemon's process ID to pid-file. The default is Create ncpus worker threads to take advantage of multiple CPUs. By default, tries to determine the number of CPUs present and creates one thread per CPU. If it cannot determine the number of CPUs, it creates a single worker thread. Send DNS lookups to port number query-port when querying name servers. This provides a way of testing the lightweight resolver daemon with a name server that listens for queries on a nonstandard port number. Listen for lightweight resolver queries on the loopback interface using UDP port number port. The default is port 921. Write memory usage statistics to standard output on exit. This option is only of interest to BIND 9 developers and may be removed or changed in a future release. Change root to directory immediately after reading the configuration file (see chroot(2)). Run as user-id, which is a user name or numeric ID that must be present in the password file. changes its user-id after it has carried out any privileged operations, such as writing the process-ID file or binding a socket to a privileged port (typically any port less than 1024). Note is a daemon for lightweight resolvers, not a lightweight daemon for resolvers. AUTHOR
was developed by the Internet Systems Consortium (ISC). FILES
Default resolver configuration file Default process-id file SEE ALSO
named(1M), chroot(2). available online at available from the Internet Systems Consortium at BIND 9.3 lwresd(1M)
All times are GMT -4. The time now is 04:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy