Visit Our UNIX and Linux User Community

Special Forums Windows & DOS: Issues & Discussions Home Questions Tags Users Unanswered Windows 2016 DNS server returns SERVFAIL for non-existing doma Post 303043612 by MadeInGermany on Sunday 2nd of February 2020 05:31:36 AM
Old 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:
 
Test Your Knowledge in Computers #224
Difficulty: Easy
In September 2019, according to NetMarketShare, Windows had just over 87% of the global desktop market, followed by Linux at close to 10%, and macOS in third place at around 2%.
True or False?

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ftp server on old home computer - a few questions

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

Install Windows 2003 R2 on existing Windows 2008

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

dlsym() returns 0 for an existing function

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

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

5. UNIX for Advanced & Expert Users

Yahoo Interview unanswered questions

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

DNS: Dig returns different responses...

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

Stack Overflow Questions Tags Users Badges Unanswered Ask Question Ask for the explanation of types

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

Tilde prefix returns invalid home directory.

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

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
resolver(5)						      BSD File Formats Manual						       resolver(5)

NAME
resolver -- resolver configuration file format DESCRIPTION
The resolver is a set of routines in the C library resolv(3) that provide access to the Internet Domain Name System (DNS). A resolver con- figuration file contains information used to specify parameters for a DNS resolver client. The file contains a list of keywords with values that provide various types of resolver information. Mac OS X supports a DNS search strategy that may involve multiple DNS resolver clients. See the SEARCH STRATEGY section below for an over- view of multi-client DNS search. Each DNS client is configured using the contents of a single configuration file of the format described below, or from a property list sup- plied from some other system configuration database. Note that the /etc/resolv.conf file, which contains configuration for the default (or "primary") DNS resolver client, is maintained automatically by Mac OS X and should not be edited manually. Changes to the DNS configuration should be made by using the Network Preferences panel. The different configuration options are given below. nameserver Internet address (in dot notation for IPv4 or in colon notation for IPv6) of a name server that the resolver should query. The address may optionally have a trailing dot followed by a port number. For example, 10.0.0.17.55 specifies that the nameserver at 10.0.0.17 uses port 55. Up to MAXNS (currently 3) name servers may be listed, one per keyword. If there are multiple servers, the resolver library queries them in the order listed. The algorithm used is to try a name server, and if the query times out, try the next, until out of name servers, then repeat trying all the name servers until a maximum number of retries are made. port IP port number to be used for this resolver. The default port is 53. The port number for an individual nameserver may be specified as part of the nameserver address (see nameserver above) to override the default or the port number specified as a value for this keyword. domain Domain name associated with this resolver configuration. This option is normally not required by the Mac OS X DNS search system when the resolver configuration is read from a file in the /etc/resolver directroy. In that case the file name is used as the domain name. However, domain must be provided when there are multiple resolver clients for the same domain name, since multiple files may not exist having the same name. See the SEARCH STRATEGY section for more details. search Search list for host-name lookup. This parameter is only used by the "Super" DNS resolver, which manages the DNS search strategy amongst multiple DNS resolver clients. Unqualified queries will be attempted using each component of the search list in turn until a match is found. Note that this process may be slow and will generate a lot of network traffic if the servers for the listed domains are not local, and that queries will time out if no server is available for one of the domains. The search list is currently limited to six domains with a total of 256 characters. search_order Only required for those clients that share a domain name with other clients. Queries will be sent to these clients in order by ascending search_order value. For example, this allows two clients for the ".local" domain, which is used by Apple's Rendezvous multicast DNS system, but which may also be used at some sites as private DNS domain name. sortlist Sortlist allows addresses returned by gethostbyname to be sorted. A sortlist is specified by IP address netmask pairs. The netmask is optional and defaults to the natural netmask of the net. The IP address and optional network pairs are separated by slashes. Up to 10 pairs may be specified. For example: sortlist 130.155.160.0/255.255.240.0 130.155.0.0 timeout Specifies the total amount of time allowed for a name resolution. This time interval is divided by the number of nameservers and the number of retries allowed for each nameserver. options Options allows certain internal resolver variables to be modified. The syntax is: options option ... where option is one of the following: debug sets RES_DEBUG in the resolver options. timeout:n sets the per-retry timeout for resolver queries. The total timeout allowed for a query depends on the number of retries and the number of nameservers. This value is ignored if a total timeout is specified using the timeout keyword (see above). ndots:n Sets a threshold for the number of dots which must appear in a name given to res_query (see resolver(3)) before an initial absolute query will be made. The default for n is ``1'', meaning that if there are any dots in a name, the name will be tried first as an absolute name before any search list elements are appended to it. The keyword and value must appear on a single line, and the keyword must start the line. The value follows the keyword, separated by white space. SEARCH STRATEGY
Mac OS X uses a DNS search strategy that supports multiple DNS client configurations. Each DNS client has its own set of nameserver addresses and its own set of operational parameters. Each client can perform DNS queries and searches independent of other clients. Each client has a symbolic name which is of the same format as a domain name, e.g. "apple.com". A special meta-client, known as the "Super" DNS client acts as a router for DNS queries. The Super client chooses among all available clients by finding a best match between the domain name given in a query and the names of all known clients. Queries for qualified names are sent using a client configuration that best matches the domain name given in the query. For example, if there is a client named "apple.com", a search for "www.apple.com" would use the resolver configuration specified for that client. The match- ing algorithm chooses the client with the maximum number of matching domain components. For example, if there are clients named "a.b.c", and "b.c", a search for "x.a.b.c" would use the "a.b.c" resolver configuration, while a search for "x.y.b.c" would use the "b.c" client. If there are no matches, the configuration settings in the default client, generally corresponding to the /etc/resolv.conf file or to the "pri- mary" DNS configuration on the system are used for the query. If multiple clients are available for the same domain name, the clients ordered according to a search_order value (see above). Queries are sent to these resolvers in sequence by ascending value of search_order. The configuration for a particular client may be read from a file having the format described in this man page. These are at present located by the system in the /etc/resolv.conf file and in the files found in the /etc/resolver directroy. However, client configurations are not limited to file storage. The implementation of the DNS multi-client search strategy may also locate client configuratins in other data sources, such as the System Configuration Database. Users of the DNS system should make no assumptions about the source of the configuration data. FILES
/etc/resolv.conf, /etc/resolver/* SEE ALSO
gethostbyname(2), getaddrinfo(3), resolver(3) Mac OS June 6, 2003 Mac OS

Featured Tech Videos

All times are GMT -4. The time now is 06:24 PM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy