07-06-2012
Remove this servers' IP addresses from resolv.conf, and further, stop and disable the named service on it. After this, your host will use only the master and slave DNS servers and so should always be accurate.
(If for some reason this presents a peformance issue, then we will look at creating a proper dns caching-resolver on this server.)
This User Gave Thanks to otheus For This Post:
9 More Discussions You Might Find Interesting
1. Solaris
I just installed Solaris 6/10 without any problems but I didn't connect the network cable when I installed it.
Here are my problems:
-I can access webpages using IP addrsses but not with domain names
-ssh is installed but it is not running ('ps -e | grep sshd' didn't show it)
I have been... (4 Replies)
Discussion started by: kungpow
4 Replies
2. HP-UX
Dear frnds,
i just migrated to hp_ux11i from digital unix, from my new system some printers not printing next day, what i mean is, in lpstat it shows printer is enabled but printing not happening. for that what i do u know, i just disable the lp and enable it again. then it would print. is there... (0 Replies)
Discussion started by: jestinabel
0 Replies
3. UNIX for Dummies Questions & Answers
hi guys
I am doing some testing for DNS
I got a master DNS(192.168.2.10) and I setup a slave DNS(192.168.2.11) but when I shutdown the Master DNS my linux client cannot resolve using the slave
any idea way?
This is the named.conf
options
{
query-source port 53;
directory... (9 Replies)
Discussion started by: kopper
9 Replies
4. Solaris
Hi All,
I have configured linux server as local dns server (practice level).
I have given the IP and hostname details in /etc/hosts
-bash-3.00# cat /etc/hosts
#
# Internet host table
#
::1 localhost
127.0.0.1 localhost
192.168.1.78 dummy.set.com loghost
192.168.1.57 cent.set.com #... (3 Replies)
Discussion started by: vaibhav.kanchan
3 Replies
5. Red Hat
Hi,
I have installed RHEL5 as a new build and need get it to resolve to the internet. At the moment I get following:
# dig www.google.com
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5 <<>> www.google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status:... (9 Replies)
Discussion started by: Duffs22
9 Replies
6. Red Hat
Hi All,
Distros of machines : RHEL6
Bind Vesrion : Bind-9.7-3.2
I am trying to set up a test DNS for my home network. I have two rhel 6 machines A and B. Machine A has 2 NICs and is acting as a router also, one NIC is facing intranet and the otehr is facing intranet. On machine A i have... (0 Replies)
Discussion started by: Rohit Bhanot
0 Replies
7. Shell Programming and Scripting
Hello to all,
May you help saying me how to flush a specific domain in Linux SunOS5
I know the command rndc is to flush DNS cache, but I would like to know:
1- How to do a flush only on specific domain
2- How to see the content of DNS Resolver cache (similar to info given by IPCONFIG... (2 Replies)
Discussion started by: Ophiuchus
2 Replies
8. Proxy Server
Hi there,
I have a VPS and am working on a little side project for myself and friend which is a DNS proxy. Everything was great till recently. My VPS IP has been detected by some botnet or something, and I believe SMURF attacks are occuring. The VPS provider keeps shutting down my VPS... (3 Replies)
Discussion started by: phi0x
3 Replies
9. 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)