Sponsored Content
Top Forums UNIX for Advanced & Expert Users One of the two DNS server going down causes impacts Post 303043091 by broy32000 on Saturday 18th of January 2020 01:22:43 AM
Old 01-18-2020
Hi Neo,
First level failure: The CPU DNS server (Windows DC) spiked. This DNS server appears as the 2nd server in /etc/resolv.conf file.
Second (result of the 1st): Application servers were unable to connect to DB server. Logs reported --unable to find DB connection stream

When we reproduced the situation (kept 2nd DNS server down), the application server was unable to connect to DB server. But "nslookup <host> " worked

--- Post updated at 07:22 AM ---

Neo,
Also please note that fixing the root cause (CPU spike or death of one DNS server) is not what I want. I want to solve the fact that resiliency did not work-- why app servers were unable to connect while only DNS server out of two was down.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Impacts on Timezone changes

I'm running on UNIX with Solaris. I need to change the Timezone on the box and was going to make the changes to the files and then reboot the box. Someone warned me that this method should not be used and that a util (unconfig.sys I think it was) should be used to make the changes. Any ideas... (2 Replies)
Discussion started by: Lextar
2 Replies

2. UNIX for Dummies Questions & Answers

dns server

Hi all, I need to know step by step procedure to configure and to test a dns server on redhatlinux 7.2. thanks and reg, bache gowda (4 Replies)
Discussion started by: bache_gowda
4 Replies

3. UNIX for Dummies Questions & Answers

DNS Server help

Hi, I would like to create an internal webpage for my company that would only be viewable when connected to the VPN or internal network. I want a webpage like newsite.company.com. Is there a way to do this. We obviously already have www.company.com, but how would I go about creating the newsite.... (1 Reply)
Discussion started by: ejbrever
1 Replies

4. UNIX for Dummies Questions & Answers

setup a DNS server for my redhat server

Using Redhat Linux Enterprise AS 4 can someone teach me how to setup a dns server for my webserver? i've registered a domainname at mydomain.com but when i type in the domain i register i cannot enter to my webserver. someone told me that it is related with the DNS setting on my server. i've... (2 Replies)
Discussion started by: kaixiang88
2 Replies

5. Solaris

Solaris DNS Client For Microsoft DNS Server

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

6. HP-UX

Impacts on upgrading the aCC compiler in HP-UX

Hi, We are currently using the aCC 3.13 compiler in HP-UX 11.0 but we need to upgrade the aCC compiler version from aCC 3.13 to aCC3.31. 1. Is there any major impact of update the compiler? 2. What are the major things we need to make sure before updating the compiler? Can any one guide... (2 Replies)
Discussion started by: gyanusoni
2 Replies

7. AIX

Impacts of emptying /var/adm/wtmp file ?

In our operating procedures, if a workstation has a space problem in the /var filesystem, one of the most frequent case we were told is the size of the /var/adm/wtmp file. Someone once told me it is dangerous to do this. Is it ? I cannot say for certain that whomever wrote that procedure is... (2 Replies)
Discussion started by: Browser_ice
2 Replies

8. 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

9. Solaris

DNS Server help

Hi Team, I need to find the clients which are being served by the DNS server in our environment. The approach currently i am having is to look for the DNS server IP in nameserver IP in the /etc/resolv.conf file in all the servers in our environment. Do we have any command(s) which gives... (1 Reply)
Discussion started by: vishalaswani
1 Replies

10. Solaris

DNS client added to DNS server but not working

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
LWRESD(8)							       BIND9								 LWRESD(8)

NAME
lwresd - lightweight resolver daemon SYNOPSIS
lwresd [-c config-file] [-C config-file] [-d debug-level] [-f] [-g] [-i pid-file] [-m flag] [-n #cpus] [-P port] [-p port] [-s] [-t directory] [-u user] [-v] [-4] [-6] 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 completes, 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
-4 Use IPv4 only even if the host machine is capable of IPv6. -4 and -6 are mutually exclusive. -6 Use IPv6 only even if the host machine is capable of IPv4. -4 and -6 are mutually exclusive. -c config-file Use config-file as the configuration file instead of the default, /etc/lwresd.conf. -c can not be used with -C. -C config-file Use config-file as the configuration file instead of the default, /etc/resolv.conf. -C can not be used with -c. -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. -i pid-file Use pid-file as the PID file instead of the default, /var/run/lwresd/lwresd.pid. -m flag Turn on memory usage debugging flags. Possible flags are usage, trace, record, size, and mctx. These correspond to the ISC_MEM_DEBUGXXXX flags described in <isc/mem.h>. -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 security on most systems; the way chroot(2) 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 Systems Consortium COPYRIGHT
Copyright (C) 2004, 2005, 2007-2009 Internet Systems Consortium, Inc. ("ISC") Copyright (C) 2000, 2001 Internet Software Consortium. BIND9 June 30, 2000 LWRESD(8)
All times are GMT -4. The time now is 04:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy