Sponsored Content
Full Discussion: HP-UX DNS issue
Operating Systems HP-UX HP-UX DNS issue Post 302886967 by agonza07 on Tuesday 4th of February 2014 04:52:42 PM
Old 02-04-2014
HP HP-UX DNS issue

Hi All,

I'm having some problems with our HP-UX environment. I'm running Oracle EBS on a HP-UX system, and whenever my primary dns server goes down some of my clients can no longer connect. Everything on my windows side continues to work, and clients can reach the internet and other services without a problem, so my best guess is that it is only a problem with my HP-UX system.

I have a secondary dns server defined so I'm not sure why it's not failing over? Is there a timeout issue, or something else I'm missig here? Please see below for how my conf files look like.

resolve.conf
domain domain.local
nameserver 192.168.1.1
nameserver 192.168.1.2

nsswitch.conf
hosts: files [NOTFOUND=continue UNAVAIL=continue] dns [NOTFOUND=return UNAVAIL=continue TRYAGAIN=return]
 

10 More Discussions You Might Find Interesting

1. IP Networking

DNS issue.

Hi, We use linux as a DNS server for our local network. ( linuxnol.nollekens.be ) We can ping this machine on all our XP clients like this: C:\>ping linuxnol Until yesterday it was on our XP clients enough to type "ping ibm250" ( our 2de unix server, an AIX ). But after a shutdown of this... (1 Reply)
Discussion started by: progressdll
1 Replies

2. UNIX for Advanced & Expert Users

DNS issue still not looking in files

anyone ever seen this problem with /etc/nsswitch.conf forcing the system to look in files then dns but the system ignores the files and goes off check the dn servers is there any further config I've missed ??? /etc/resolve.conf name servers >>>> boring IPS /etc/nsswitch.conf is set to... (5 Replies)
Discussion started by: kie
5 Replies

3. Solaris

t2000 DNS issue

I have an issue with DNS on a solaris t2000 When I set up the zones there was an issue with the /etc/resolv.conf, I had made a typo in my DNS server. I only noticed this after creating my new zones. I have corrected this in the global zone and I am now able to ping and nslookup inthe... (2 Replies)
Discussion started by: james dewitt
2 Replies

4. Red Hat

Linux DNS issue

Hi , I have configured OEL 5.3 server on VMware server,installation went fine, however when i am checking host using configured /etc/hosts i am getting following error let me know where it went wrong . I had disabled firewall options and SELLinux. root@oen11g ~]# host oen11g.grid.com ;;... (2 Replies)
Discussion started by: autoconfig
2 Replies

5. Red Hat

DNS issue in Redhat 9

Hi all m newbie in linux and trying to setup my internal DNS server for local network.After messing with DNS for hours i am posting this. i have configured /etc/resolve.conf, hostname with domain name in /etc/sysconfig/network file,/etc/hosts file with local host entry and zone file... (1 Reply)
Discussion started by: Vaibhav.T
1 Replies

6. Red Hat

Issue in DNS set up

:wall:I am a beginer in Linux admin. I have build new DNS setting in my system. Please find the below procedure what I followed to build DNS. but at last when I fired nslookup command, its getting error. I am using RHEL5 OS. Please help me to resolve this below issue.. Advance thanks for... (1 Reply)
Discussion started by: pradipta_pks
1 Replies

7. Red Hat

dns update issue

i have redhat service as public dns i have added new entry but when i reload the named service i got this error in log the working directory is not writable (1 Reply)
Discussion started by: leganti
1 Replies

8. Red Hat

DNS Resolution Issue

Hello, Having issue resolving DNS using the IP address. Using the server Name it resolves fine. Was wondering if there is any configuration issue. # nslookup xxxxxxxx01 Server: Primary DNS IP Address: Primary DNS IP#53 Name: xxxxxxxx01.local domain Address: x.y.z.123 # nslookup... (1 Reply)
Discussion started by: ikn3
1 Replies

9. IP Networking

OS X & VPN DNS Issue

I'll try and be brief and detailed. I have a Macbook Pro Retina running Mavericks. When on my network at the office (work) everything local works just fine. Local servers are resolved through our internal DNS settings. For example, we have a fileserver at "fs01". I can connect to it with... (1 Reply)
Discussion started by: jbhardman
1 Replies

10. Linux

DNS Response Issue

Hi, I have a Windows based Domain (abc.com)servers like: 172.30.1.246 172.30.1.247 172.30.3.246 172.30.3.247 On all my Linux servers (/etc/resolv.conf) have a following DNS servers entries: nameserver 172.30.3.246 nameserver 172.30.3.247 But when i ping my Domain (abc.com), it... (5 Replies)
Discussion started by: refra
5 Replies
NSSWITCH.CONF(5)					     Linux Programmer's Manual						  NSSWITCH.CONF(5)

NAME
nsswitch.conf - Name Service Switch configuration file DESCRIPTION
The Name Service Switch (NSS) configuration file, /etc/nsswitch.conf, is used by the GNU C Library to determine the sources from which to obtain name-service information in a range of categories, and in what order. Each category of information is identified by a database name. The file is plain ASCII text, with columns separated by spaces or tab characters. The first column specifies the database name. The remaining columns describe the order of sources to query and a limited set of actions that can be performed by lookup result. The following databases are understood by the GNU C Library: aliases Mail aliases, used by getaliasent(3) and related functions. ethers Ethernet numbers. group Groups of users, used by getgrent(3) and related functions. hosts Host names and numbers, used by gethostbyname(3) and related functions. netgroup Network-wide list of hosts and users, used for access rules. C libraries before glibc 2.1 supported netgroups only over NIS. networks Network names and numbers, used by getnetent(3) and related functions. passwd User passwords, used by getpwent(3) and related functions. protocols Network protocols, used by getprotoent(3) and related functions. publickey Public and secret keys for Secure_RPC used by NFS and NIS+. rpc Remote procedure call names and numbers, used by getrpcbyname(3) and related functions. services Network services, used by getservent(3) and related functions. shadow Shadow user passwords, used by getspnam(3) and related functions. Here is an example /etc/nsswitch.conf file: passwd: compat group: compat shadow: compat hosts: dns [!UNAVAIL=return] files networks: nis [NOTFOUND=return] files ethers: nis [NOTFOUND=return] files protocols: nis [NOTFOUND=return] files rpc: nis [NOTFOUND=return] files services: nis [NOTFOUND=return] files The first column is the database name. The remaining columns specify: * One or more service specifications e.g., "files", "db", or "nis". The order of the services on the line determines the order in which those services will be queried, in turn, until a result is found. * Optional actions to perform if a particular result is obtained from the preceding service, e.g., "[NOTFOUND=return]". The service specifications supported on your system depend on the presence of shared libraries, and are therefore extensible. Libraries called /lib/libnss_SERVICE.so.X will provide the named SERVICE. On a standard installation, you can use "files", "db", "nis", and "nis- plus". For the hosts database, you can additionally specify "dns". For the passwd, group, and shadow databases, you can additionally specify "compat" (see Compatibility mode below). The version number X may be 1 for glibc 2.0, or 2 for glibc 2.1 and later. On systems with additional libraries installed, you may have access to further services such as "hesiod", "ldap", "winbind" and "wins". An action may also be specified following a service specification. The action modifies the behavior following a result obtained from the preceding data source. Action items take the general form: [STATUS=ACTION] [!STATUS=ACTION] where STATUS => success | notfound | unavail | tryagain ACTION => return | continue The ! negates the test, matching all possible results except the one specified. The case of the keywords is not significant. The STATUS value is matched against the result of the lookup function called by the preceding service specification, and can be one of: success No error occurred and the requested entry is returned. The default action for this condition is "return". notfound The lookup succeeded, but the requested entry was not found. The default action for this condition is "continue". unavail The service is permanently unavailable. This can mean either that the required file cannot be read, or, for network ser- vices, that the server is not available or does not allow queries. The default action for this condition is "continue". tryagain The service is temporarily unavailable. This could mean a file is locked or a server currently cannot accept more connec- tions. The default action for this condition is "continue". The ACTION value can be one of: return Return a result now. Do not call any further lookup functions. continue Call the next lookup function. Compatibility mode (compat) The NSS "compat" service is similar to "files" except that it additionally permits special entries in /etc/passwd for granting users or members of netgroups access to the system. The following entries are valid in this mode: +user Include the specified user from the NIS passwd map. +user:::::: Include the specified user from the NIS passwd map, but override with non-empty passwd fields. +@netgroup Include all users in the given netgroup. -user Exclude the specified user from the NIS passwd map. -@netgroup Exclude all users in the given netgroup. + Include every user, except previously excluded ones, from the NIS passwd map. By default the source is "nis", but this may be overridden by specifying "nisplus" as the source for the pseudo-databases passwd_compat, group_compat, and shadow_compat. FILES
A service named SERVICE is implemented by a shared object library named libnss_SERVICE.so.X that resides in /lib. /etc/nsswitch.conf NSS configuration file. /lib/libnss_compat.so.X implements "compat" source. /lib/libnss_db.so.X implements "db" source. /lib/libnss_dns.so.X implements "dns" source. /lib/libnss_files.so.X implements "files" source. /lib/libnss_hesiod.so.X implements "hesiod" source. /lib/libnss_nis.so.X implements "nis" source. /lib/libnss_nisplus.so.X implements "nisplus" source. NOTES
Within each process that uses nsswitch.conf, the entire file is read only once. If the file is later changed, the process will continue using the old configuration. Traditionally, there was only a single source for service information, often in the form of a single configuration file (e.g., /etc/passwd). However, as other name services, such as the Network Information Service (NIS) and the Domain Name Service (DNS), became popular, a method was needed that would be more flexible than fixed search orders coded into the C library. The Name Service Switch mecha- nism, which was based on the mechanism used by Sun Microsystems in the Solaris 2 C library, introduced a cleaner solution to the problem. SEE ALSO
getent(1), nss(5) COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2012-04-14 NSSWITCH.CONF(5)
All times are GMT -4. The time now is 03:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy