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
dns(n)									dns								    dns(n)

NAME
dns - Tcl Domain Name Service Client SYNOPSIS
package require Tcl 8.2 package require dns ?1.0.1? ::dns::resolve query ?options? ::dns::configure ?options? ::dns::name token ::dns::address token ::dns::cname token ::dns::status token ::dns::error token ::dns::reset token ::dns::wait token ::dns::cleanup token DESCRIPTION
The dns package provides a Tcl only Domain Name Service client. You should refer to RFC 1034 and RFC 1035 for information about the DNS protocol or read resolver(3) to find out how the C library resolves domain names. The intention of this package is to insulate Tcl scripts from problems with using the system library resolver for slow name servers. It may or may not be of practical use. The package also extends the package uri to support DNS URIs or the form dns:what.host.com or dns://my.nameserver/what.host.com. The dns::resolve command can handle DNS URIs or simple domain names as a query. Note: This package uses TCP to query DNS servers as the tcl core does not implement UDP networking. This means that this module will not work if DNS over TCP is blocked by a firewall, or not accepted by the chosen nameserver. COMMANDS
::dns::resolve query ?options? Resolve a domain name using the DNS protocol. query is the domain name to be lookup up. This should be either a fully qualified domain name or a DNS URI. -nameserver hostname or -server hostname Specify an alternative name server for this request. -protocol tcp|udp Specify the network protocol to use for this request. Can be one of tcp or udp. However only tcp is currently implemented in the package. -port portnum Specify an alternative port. -search domainlist -timeout milliseconds Override the default timeout. -type TYPE Specify the type of DNS record you are interested in. Valid values are A, NS, MD MF, CNAME, SOA, MB, MG, MR, NULL, WKS, PTR, HINFO, MINFO, MX, TXT, AXFR, MAILB, MAILA and *. See RFC1035 for details about the return values. -class CLASS Specify the class of domain name. This is usually IN but may be one of IN for internet domain names, CS, CH, HS or * for any class. -recurse boolean Set to false if you do not want the name server to recursively act upon your request. Normally set to true. -command procname Set a procedure to be called upon request completion. The procedure will be passed the token as its only argument. ::dns::configure ?options? The ::dns::configure command is used to setup the dns package. The server to query, the protocol and domain search path are all set via this command. If no arguments are provided then a list of all the current settings is returned. If only one argument then it must the the name of an option and the value for that option is returned. -nameserver hostname Set the default name server to be used by all queries. The default is localhost. -protocol tcp|udp Set the default network protocol to be used. Defaults to tcp. -port portnum Set the default port to use on the name server. The default is 53. -search domainlist Set the domain search list. This is currently not used. -timeout milliseconds Set the default timeout value for DNS lookups. Defaults to 30 seconds. ::dns::name token Returns a list of all domain names returned as an answer to your query. ::dns::address token Returns a list of the address records that match your query. ::dns::cname token Returns a list of canonical names (usually just one) matching your query. ::dns::status token Returns the status flag. For a successfully completed query this will be ok. May be error or timeout or eof. See also ::dns::error ::dns::error token Returns the error message provided for requests whose status is error. If there is no error message then an empty string is returned. ::dns::reset token Reset or cancel a DNS query. ::dns::wait token Wait for a DNS query to complete and return the status upon completion. ::dns::cleanup token Remove all state variables associated with the request. EXAMPLES
% set tok [dns::resolve www.tcl.tk] ::dns::1 % dns::status $tok ok % dns::address $tok 199.175.6.239 % dns::name $tok www.tcl.tk Using DNS URIs as queries: % set tok [dns::resolve "dns:tcl.tk;type=MX"] % set tok [dns::resolve "dns://l.root-servers.net/www.tcl.tk"] SEE ALSO
resolver(5) AUTHORS
Pat Thoyts KEYWORDS
DNS, resolver, domain name service dns 1.0.1 dns(n)
All times are GMT -4. The time now is 08:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy