10-15-2012
Try nscd --help To get the option that reports cache information.
The name service daemon keeps track of catch hits and fails.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Guys need some advice on how to check some of the questions below?
i'm running on an open VMS platform... which i am an idiot to...
appreciate if anyone can give some hints or source on how to check on..
a script that is running on cron job... but doesn't run as the login user name..
1. why... (6 Replies)
Discussion started by: 12yearold
6 Replies
2. Solaris
hey guys, how to add soalris box as a microsoft DNS Client ?
and how to register in the microsoft DNS ??
i managed to query from the DNS server after adding /etc/resolve.conf and editing /etc/nsswitch.conf
but i need to register the soalris server (dns Client) into Microsoft DNS automatically.... (3 Replies)
Discussion started by: mduweik
3 Replies
3. Shell Programming and Scripting
hi guys
Well, i need to have a report generation script or any script which will show me all the content/information of a file when i run that script.
Please help me on this isssue at the earliest.As i am little bit aware of scripting.Thanks in advance!
regards
ash (4 Replies)
Discussion started by: whizkidash
4 Replies
4. Homework & Coursework Questions
Any help on like where to get started on this? I'm just confused.
1. The problem statement, all variables and given/known data:
Enter text here.Queries to satisfy these two report requests (use your CCI database):
Retrieve all rows of active inventory where current on hands is less than... (0 Replies)
Discussion started by: lakers34kb
0 Replies
5. UNIX for Advanced & Expert Users
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
6. Red Hat
Hi,
I have a question on how to point the DNS server-1's A-record to second DNS server, which is DNS server-2. So, the computer can access other domain which only listed in the DNS server-2. The scenario is as follow:
http://img689.imageshack.us/img689/6333/12234.png
How to configure this... (4 Replies)
Discussion started by: Paris Heng
4 Replies
7. Red Hat
I am trying to setup a CentOS 6.2 server that will be doing 3 things DHCP, DNS & Samba for a very small office (2 users). The idea being this will replace a very old Win2k server. The users are all windows based clients so only the server will be Linux based.
I've installed CentOS 6.2 with... (4 Replies)
Discussion started by: FireBIade
4 Replies
8. Programming
can these 3 be combined into 1 query?
createtablea1as
selecta.tps_Res_nb,
b.tkt_prod_cd,
b.tkt_prod_typ_nm,
b.prod_intrnl_ds,
b.tkt_prod_typ_nm AS TKT_ENTL_NM,
casewhen b.tkt_prod_nm isnotnullthen b.tkt_prod_nm
when b.tkt_prod_nm isnulland b.prod_intrnl_ds isnotnullthen... (1 Reply)
Discussion started by: dwr80
1 Replies
9. AIX
We have 3PVs, now we want to migrate it to new 2PVs.
OLD PVS
hdisk1 ---- /u01
hdisk2 ------ /u01
hdisk 3 ----- /u02, /u01
new PVs
hdisk4 ---- Free
hdisk5 ---- Free
I check man, it doesn't say anything about offline/online thing, do i need downtime to migrate pv ? also, what i... (6 Replies)
Discussion started by: Fracker
6 Replies
10. Solaris
Hi,
We have built a new server (RHEL VM)and added that IP/hostname into dns zone configs file on DNS server (Solaris 10). Reloaded the configuration using
and added nameserver into resolv.conf on client. But when I am trying nslookup, its not getting resolved. The nameserver is not able to... (8 Replies)
Discussion started by: snchaudhari2
8 Replies
LEARN ABOUT REDHAT
lwresd
LWRESD(8) LWRESD(8)
NAME
lwresd - lightweight resolver daemon
SYNOPSIS
lwresd [ -C config-file ] [ -d debug-level ] [ -f ] [ -g ] [ -i pid-file ] [ -n #cpus ] [ -P port ] [ -p port ] [ -s ] [ -t direc-
tory ] [ -u user ] [ -v ]
DESCRIPTION
lwresd is the daemon providing name lookup services to 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.
lwresd listens for resolver queries on a UDP port on the IPv4 loopback interface, 127.0.0.1. This means that lwresd can only be used by
processes running 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 the server which then resolves them using the DNS protocol. When the DNS lookup com-
pletes, lwresd encodes the answers in the lightweight resolver format and returns them to the client that made the request.
If /etc/resolv.conf contains any nameserver entries, lwresd sends recursive DNS queries to those servers. This is similar to the use of
forwarders in a caching name server. If no nameserver entries are present, or if forwarding fails, lwresd resolves the queries autonomously
starting at the root name servers, using a built-in list of root server hints.
OPTIONS
-C config-file
Use config-file as the configuration file instead of the default, /etc/resolv.conf.
-d debug-level
Set the daemon's debug level to debug-level. Debugging traces from lwresd become more verbose as the debug level increases.
-f Run the server in the foreground (i.e. do not daemonize).
-g Run the server in the foreground and force all logging to stderr.
-n #cpus
Create #cpus worker threads to take advantage of multiple CPUs. If not specified, lwresd will try to determine the number of CPUs
present and create one thread per CPU. If it is unable to determine the number of CPUs, a single worker thread will be created.
-P port
Listen for lightweight resolver queries on port port. If not specified, the default is port 921.
-p port
Send DNS lookups to port port. If not specified, the default is port 53. This provides a way of testing the lightweight resolver
daemon with a name server that listens for queries on a non-standard port number.
-s Write memory usage statistics to stdout on exit.
Note: This option is mainly of interest to BIND 9 developers and may be removed or changed in a future release.
-t directory
chroot() to directory after processing the command line arguments, but before reading the configuration file.
Warning: This option should be used in conjunction with the -u option, as chrooting a process running as root doesn't enhance secu-
rity on most systems; the way chroot() is defined allows a process with root privileges to escape a chroot jail.
-u user
setuid() to user after completing privileged operations, such as creating sockets that listen on privileged ports.
-v Report the version number and exit.
FILES
/etc/resolv.conf
The default configuration file.
/var/run/lwresd.pid
The default process-id file.
SEE ALSO
named(8), lwres(3), resolver(5).
AUTHOR
Internet Software Consortium
BIND9 June 30, 2000 LWRESD(8)