02-02-2020
That's a secret that nobody could solve in over a decade. Why do Windows DNS servers return SERVFAIL rather than NXDOMAIN?
IMHO a severe bug. Effectively it disables the caching of an unsuccessful host lookup; makes a performance difference, especially with a thousand DNS clients that run buggy software. But the customer insisted on Windows DNS.
Perhaps somebody here has a solution by chance. Otherwise this is a question for a Windows forum...
Okay, a mitigation I can offer: have the non-Windows nameserver first in /etc/resolv. conf
Last edited by MadeInGermany; 02-02-2020 at 09:39 AM..
Reason: typo
This User Gave Thanks to MadeInGermany For This Post:
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi!
Very new to unix stuff, and this is my first post to the forum. I'm pretty sure I know enough to know I know nothing, so please be patient with me and don't laugh too hard.
Ok, I've got an old computer and a laptop - the old computer was bought in the mid 90's it's still running windows... (1 Reply)
Discussion started by: boredbody
1 Replies
2. Windows & DOS: Issues & Discussions
Hi,
I am trying to install WIndows 2003 R2 Server on existing Windows 2008 server. When I run the 2003 cd it says no disk found. What can be the problem. (2 Replies)
Discussion started by: gunnervarma
2 Replies
3. UNIX for Dummies Questions & Answers
Sometimes I observe this in gdb:
(gdb) br my_function
Breakpoint .. at 0x...: file ..., line ...
i.e., "my_function" does exist in the current executable.
however, dlsym does not find it:
(gdb) p dlsym(0,"my_function")
$6 = 0
This is a C program; dlsym does find other defined functions and... (2 Replies)
Discussion started by: sds
2 Replies
4. 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
5. UNIX for Advanced & Expert Users
Hi guys,
please help me get the answers of these questions which I faced in an interview @ Yahoo
1. I want to " ls " few million files, certainly I cannot do so because ls has some restriction in KBs, how can I do it alternatively.
2. Change the system in such a way that while booting up,... (2 Replies)
Discussion started by: gauravsharma29
2 Replies
6. IP Networking
Hey everyone,
Okay, so I've been having some fun with the dig command, and wanted to dig my old school. Two questions came up from this. So I:
dig @8.8.8.8 +recurse njcu.edu ANY
and the result is about 8 records, including the SOA record. One of them is this weird TXT record, and the other is... (1 Reply)
Discussion started by: Lost in Cyberia
1 Replies
7. Hardware
I have read a document which tells me the following 4 things are done by the RAM embedded on disk driver controller. But I don't know what's difference between buffer and cache. Thanks!
RAM on disk drive controllers
1 firmware
2 speed matching buffer
3 prefetching buffer
4 cache (1 Reply)
Discussion started by: 915086731
1 Replies
8. Solaris
I am trying to find the home directory of users on a UNIX (Solaris/AIX) box using
echo ~usernameThis does return the home directory for all valid users. For some reason this command also outputs home directory which are non-existent for few users who seem not to have logon access to that... (31 Replies)
Discussion started by: thinkster
31 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)