Sponsored Content
Operating Systems Linux Red Hat DNS A-Record point to another DNS Post 302559262 by mark54g on Monday 26th of September 2011 02:43:16 PM
Old 09-26-2011
It depends on what operating system that the client uses. The resolv.conf on Linux can contain a set of domains to append, in order, when searching for non FQDN names in the lookup.

Windows has a similar construct, but I am unsure of how that is implemented.
 

10 More Discussions You Might Find Interesting

1. IP Networking

Dns

I would like to set up a DNS on my system, just to learn really, how difficult and what all is involved in the set up? How difficult? (6 Replies)
Discussion started by: jo calamine
6 Replies

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

3. UNIX for Dummies Questions & Answers

Configuring DNS MX record

I now know that I have to configure dns mx to actually be able to send email correctly to my mail. I have the link(user guide) on how to do this : http://bobcares.com/blog/?p=29 but where do I configure it? Is there a specific file for the configuration? I really don't understand this part. (2 Replies)
Discussion started by: anaigini45
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. IP Networking

DNS does all slave Name Server must be in the zone Resource Record file?

Hy guys, I've a problem configuring my Name Server (using bind 9) which is I'ts always necessary to put all slave Name Server for a zone in the zone resource record file or db (as you prefer)? I've this scenario: A - my domain which is son of some TLD and I delegated into two new domains B... (1 Reply)
Discussion started by: pharaoh
1 Replies

6. Red Hat

DHCP & DNS - Clients get IP but don't register in DNS

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

7. UNIX for Dummies Questions & Answers

How to Create a new internal DNS CNAME record

I need to create a new internal DNS CNAME record called "project.omc.eod" that points to a server called SPARC27.ds.eod. This is my first time doing this and any help would be greatly appreciated. Thanks in advance (10 Replies)
Discussion started by: mikeade
10 Replies

8. Red Hat

[Solved: Missing A Record] DNS issue

Hi, I have recently built a new DNS server and created a new zone. I use an ESMTP server to handle mail and the new domain has been added to this. I can send mail to gmail and other domain addresses but unable to send it to one particular domain. (DSN:Service Unavailable) DNS... (2 Replies)
Discussion started by: Duffs22
2 Replies

9. UNIX for Dummies Questions & Answers

How to update DNS record in Solaris 5.10?

Hi I have a DNS server running on Solaris 5.10, I need to update ip address of two urls defined on our dns server how do i do that? and do i need to restart dns/named service after? how do i restart the service? Thanks (4 Replies)
Discussion started by: arocker
4 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
resolv.conf(4)						     Kernel Interfaces Manual						    resolv.conf(4)

NAME
resolv.conf - Resolver configuration file SYNOPSIS
/etc/resolv.conf DESCRIPTION
The resolver is a set of routines in the C library (resolver(4)) that provide access to the Internet Domain Name System. The resolver con- figuration file contains information that is read by the resolver routines the first time they are invoked by a process. The file is designed to be human readable and contains a list of keywords with values that provide various types of resolver information. The keyword and value must appear on a single line, and the keyword (for example, nameserver) must start the line. The value follows the keyword, separated by white space. For example: keyword value The file format is as follows: nameserver Address Internet address (in dot notation) of a name server that the resolver should query. 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. If no nameserver entries are present, the default is to use the name server on the local machine. (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). domain DomainName Local domain name. Most queries for names within this domain can use short names relative to the local domain. If no domain entry is present, the domain is determined from the local host name returned by gethostname(); the domain part is taken to be everything after the first . (dot). Finally, if the host name does not contain a domain part, the root domain is assumed. search Domain_Name1 DomainName2 ... Search list for host-name lookup. Up to six domains (separated by spaces or tabs) with a total of 256 characters can be specified. If no search entry is present, the search list consists of the local domain name. Most resolver queries will be attempted using each component of the search path 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. You can also specify a search list on a per-process basis by specifying the LOCALDOMAIN environment variable. See resolver(4). The domain and search keywords are mutually exclusive. If more than one instance of these keywords is present, the last instance will override. options allow_special all | { char } Option for defining valid characters in hostnames. Specify all to disable hostname checking (allow all characters) or define a set of valid characters by using the { char } syntax, where char is the character you want to allow. For example, you can allow the semicolon, underscore, and colon characters by using { ; \_ : }. Disabling hostname checking altogether is not recommended. By default, the allow_special option is not set and strict hostname checking is enforced. options ndots:n Option for hostname lookup. The n specifies the minimum number of dots a name must contain in order for resolver to look up the name as given. If the lookup fails, the search list (if specified) is applied. The range for n is from 0 to 15. If no options entry is present, the minimum number of dots is 1. You can also specify the number of dots on a per-process basis by using the RES_OPTIONS environment variable. See resolver(4). CAUTIONS
Any white space entered after the domain name is not ignored but is interpreted as part of the domain name. RELATED INFORMATION
Commands: named(8) Functions: gethostbyname(3), resolver(4) Files: hostname(5) delim off resolv.conf(4)
All times are GMT -4. The time now is 10:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy