Sponsored Content
Full Discussion: dns issues
Top Forums UNIX for Advanced & Expert Users dns issues Post 67375 by Kelam_Magnus on Tuesday 22nd of March 2005 10:18:22 PM
Old 03-22-2005
What OS is this?

In my boxes I have a file called /etc/resolv.conf which has a "search" feature to search listed domains tab delimited in the file. You must list a gateway address as well. Not the one you have in your /etc/hosts file.

it looks like this.

#cat /etc/resolv.conf
domain sbc.com
search pacbell.com ameritech.com snet.com # to search each domain for a host used by nslookup or other feature...
nameserver IP # DNS servers to search the internal company network.
nameserver IP
nameserver IP


Also, there is a file on mine called /etc/nsswitch.conf which has a hierarchy, search, can be in any order: nis/files/dns for other hosts, but I think that is more for clustered or for boxes in the same infrastructure.
 

10 More Discussions You Might Find Interesting

1. Ubuntu

Linux Redhat ES 4.0 - DNS Config Issues

Hello all, I've a very strange thing hapenning in my Sys, I've configured the IP, DNS eveything for my internat connection, but Im only able to browse Redhat.com websites. I cant open anyother site!!! :eek: Im sure the internet is configured 'coz it displays the list of avail updates for... (11 Replies)
Discussion started by: AbhijithS
11 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. IP Networking

DNS upgrade issues, bind9.5.0_P1

so we had bind 9.3.0... we upgraded to 9.5.0 patch 1 we kept the exact same named.conf now we have a problem that some DMZ server cant do lookups from our DNS slave anymore. in the named.log we see things like this: 22-Jul-2008 16:05:04.694 security: info: client <our DMZ servers... (2 Replies)
Discussion started by: robsonde
2 Replies

4. Solaris

Solaris 10 - DNS / Issues / Help

Hi all Long time no speak, I hope you are all well. Im looking at a DNS issue here and reckon Igot a AD / DNS server issue elsewhere but need to rule out the configuration of my two server's first. IVe got the nameserver enteries in /etc/resolv.conf and dns in the /etc/nsswitch.conf ... (2 Replies)
Discussion started by: sbk1972
2 Replies

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

6. UNIX for Dummies Questions & Answers

DNS on Unix box issues

Hi Guys, Just wanted to seek your assistance on an issue encountered with one of our client DNS server query. we have 2 sets of DNS servers.. internal and external. For Internal to reach the external DNS server (DMZ) it has to go through 2 FWs. Current settings: - FW rules for Internal... (3 Replies)
Discussion started by: Hotshot8259
3 Replies

7. Red Hat

DNS A-Record point to another DNS

Hi, I have a question on how to point the DNS server-1's A-record to second DNS server, which is DNS server-2. So, the computer can access other domain which only listed in the DNS server-2. The scenario is as follow: http://img689.imageshack.us/img689/6333/12234.png How to configure this... (4 Replies)
Discussion started by: Paris Heng
4 Replies

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

9. Red Hat

DNS Server Setup Centos 6.5 Issues

I am having a bit of trouble getting my CENTOS 6.5 DNS server to work correctly in our testlab environment. Lab network is 10.8.0.0/24 in which we all access from 10.7.0.0.0/24 && 10.0.0.0/24. Here are my configs: options { listen-on port 53 { 127.0.0.1; 10.8.0.19;}; #listen-on-v6 port 53 {... (2 Replies)
Discussion started by: metallica1973
2 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 01:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy