Sponsored Content
Full Discussion: HP-UX DNS issue
Operating Systems HP-UX HP-UX DNS issue Post 302887312 by methyl on Thursday 6th of February 2014 06:56:56 PM
Old 02-06-2014
Assuming that 192.168.1.1 and 192.168.1.2 are both DNS servers and that they are Primary and Secondary respectively.

You can test whether they are both working DNS servers with:
nslookup microsoft.com 192.168.1.1
nslookup microsoft.com 192.168.2.1

The /etc/nsswitch.conf posted will give up if the Primary DNS is down.
With "NOTFOUND=return" first I don't think that your server will ever look at the secondary (or any reserve) DNS's listed in your /etc/resolv.conf .

Unless your server does tons of DNS lookups on computers which are for some reason not in your DNS, imho this is much better:

hosts: dns [NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue] files

(I cut/paste this from one of my long-term reliable computers. Not my original work and I would like to credit the tip, but it's been too long).

Last edited by methyl; 02-06-2014 at 08:02 PM..
 

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
Net::DNS::Resolver::Programmable(3)			User Contributed Perl Documentation		       Net::DNS::Resolver::Programmable(3)

NAME
Net::DNS::Resolver::Programmable - programmable DNS resolver class for offline emulation of DNS VERSION
0.003 SYNOPSIS
use Net::DNS::Resolver::Programmable; use Net::DNS::RR; my $resolver = Net::DNS::Resolver::Programmable->new( records => { 'example.com' => [ Net::DNS::RR->new('example.com. NS ns.example.org.'), Net::DNS::RR->new('example.com. A 192.168.0.1') ], 'ns.example.org' => [ Net::DNS::RR->new('ns.example.org. A 192.168.1.1') ] }, resolver_code => sub { my ($domain, $rr_type, $class) = @_; ... return ($result, $aa, @rrs); } ); DESCRIPTION
Net::DNS::Resolver::Programmable is a Net::DNS::Resolver descendant class that allows a virtual DNS to be emulated instead of querying the real DNS. A set of static DNS records may be supplied, or arbitrary code may be specified as a means for retrieving DNS records, or even generating them on the fly. Constructor The following constructor is provided: new(%options): returns Net::DNS::Resolver::Programmable Creates a new programmed DNS resolver object. %options is a list of key/value pairs representing any of the following options: records A reference to a hash of arrays containing a static set of Net::DNS::RR objects. The hash entries must be indexed by fully qualified domain names (lower-case, without any trailing dots), and the entries themselves must be arrays of the RR objects pertaining to these domain names. For example: records => { 'example.com' => [ Net::DNS::RR->new('example.com. NS ns.example.org.'), Net::DNS::RR->new('example.com. A 192.168.0.1') ], 'www.example.com' => [ Net::DNS::RR->new('www.example.com. A 192.168.0.2') ], 'ns.example.org' => [ Net::DNS::RR->new('ns.example.org. A 192.168.1.1') ] } If this option is specified, the resolver retrieves requested RRs from this data structure. resolver_code A code reference used as a call-back for dynamically retrieving requested RRs. The code must take the following query parameters as arguments: the domain, RR type, and class. It must return a list composed of: the response's RCODE (by name, as returned by Net::DNS::Header->rcode), the "aa" (authoritative answer) flag (boolean, use undef if you don't care), and the Net::DNS::RR answer objects. If an error string is returned instead of a valid RCODE, a Net::DNS::Packet object is not constructed but an error condition for the resolver is signaled instead. For example: resolver_code => sub { my ($domain, $rr_type, $class) = @_; ... return ($result, $aa, @rrs); } If both this and the "records" option are specified, then statically programmed records are used in addition to any that are returned by the configured resolver code. defnames dnsrch domain searchlist debug These Net::DNS::Resolver options are also meaningful with Net::DNS::Resolver::Programmable. See Net::DNS::Resolver for their descriptions. Instance methods The following instance methods of Net::DNS::Resolver are also supported by Net::DNS::Resolver::Programmable: search: returns Net::DNS::Packet query: returns Net::DNS::Packet send: returns Net::DNS::Packet Performs an offline DNS query, using the statically programmed DNS RRs and/or the configured dynamic resolver code. See the "new" constructor's "records" and "resolver_code" options. See the descriptions of search, query, and send for details about the calling syntax of these methods. print string: returns string searchlist: returns list of string defnames: returns boolean dnsrch: returns boolean debug: returns boolean errorstring: returns string answerfrom: returns string answersize: returns integer See "METHODS" in Net::DNS::Resolver. Currently the following methods of Net::DNS::Resolver are not supported: axfr, axfr_start, axfr_next, nameservers, port, srcport, srcaddr, bgsend, bgread, bgisready, tsig, retrans, retry, recurse, usevc, tcp_timeout, udp_timeout, persistent_tcp, persistent_udp, igntc, dnssec, cdflag, udppacketsize. The effects of using these on Net::DNS::Resolver::Programmable objects are undefined. SEE ALSO
Net::DNS::Resolver For availability, support, and license information, see the README file included with Net::DNS::Resolver::Programmable. AUTHORS
Julian Mehnle <julian@mehnle.net> perl v5.16.3 2014-06-09 Net::DNS::Resolver::Programmable(3)
All times are GMT -4. The time now is 01:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy