07-06-2012
Remove this servers' IP addresses from resolv.conf, and further, stop and disable the named service on it. After this, your host will use only the master and slave DNS servers and so should always be accurate.
(If for some reason this presents a peformance issue, then we will look at creating a proper dns caching-resolver on this server.)
This User Gave Thanks to otheus For This Post:
9 More Discussions You Might Find Interesting
1. Solaris
I just installed Solaris 6/10 without any problems but I didn't connect the network cable when I installed it.
Here are my problems:
-I can access webpages using IP addrsses but not with domain names
-ssh is installed but it is not running ('ps -e | grep sshd' didn't show it)
I have been... (4 Replies)
Discussion started by: kungpow
4 Replies
2. HP-UX
Dear frnds,
i just migrated to hp_ux11i from digital unix, from my new system some printers not printing next day, what i mean is, in lpstat it shows printer is enabled but printing not happening. for that what i do u know, i just disable the lp and enable it again. then it would print. is there... (0 Replies)
Discussion started by: jestinabel
0 Replies
3. UNIX for Dummies Questions & Answers
hi guys
I am doing some testing for DNS
I got a master DNS(192.168.2.10) and I setup a slave DNS(192.168.2.11) but when I shutdown the Master DNS my linux client cannot resolve using the slave
any idea way?
This is the named.conf
options
{
query-source port 53;
directory... (9 Replies)
Discussion started by: kopper
9 Replies
4. Solaris
Hi All,
I have configured linux server as local dns server (practice level).
I have given the IP and hostname details in /etc/hosts
-bash-3.00# cat /etc/hosts
#
# Internet host table
#
::1 localhost
127.0.0.1 localhost
192.168.1.78 dummy.set.com loghost
192.168.1.57 cent.set.com #... (3 Replies)
Discussion started by: vaibhav.kanchan
3 Replies
5. Red Hat
Hi,
I have installed RHEL5 as a new build and need get it to resolve to the internet. At the moment I get following:
# dig www.google.com
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5 <<>> www.google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status:... (9 Replies)
Discussion started by: Duffs22
9 Replies
6. Red Hat
Hi All,
Distros of machines : RHEL6
Bind Vesrion : Bind-9.7-3.2
I am trying to set up a test DNS for my home network. I have two rhel 6 machines A and B. Machine A has 2 NICs and is acting as a router also, one NIC is facing intranet and the otehr is facing intranet. On machine A i have... (0 Replies)
Discussion started by: Rohit Bhanot
0 Replies
7. Shell Programming and Scripting
Hello to all,
May you help saying me how to flush a specific domain in Linux SunOS5
I know the command rndc is to flush DNS cache, but I would like to know:
1- How to do a flush only on specific domain
2- How to see the content of DNS Resolver cache (similar to info given by IPCONFIG... (2 Replies)
Discussion started by: Ophiuchus
2 Replies
8. Proxy Server
Hi there,
I have a VPS and am working on a little side project for myself and friend which is a DNS proxy. Everything was great till recently. My VPS IP has been detected by some botnet or something, and I believe SMURF attacks are occuring. The VPS provider keeps shutting down my VPS... (3 Replies)
Discussion started by: phi0x
3 Replies
9. Solaris
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
LEARN ABOUT MINIX
resolver
RESOLVER(5) File Formats Manual RESOLVER(5)
NAME
resolver - resolver configuration file
SYNOPSIS
/etc/resolv.conf
DESCRIPTION
The resolver is a set of routines in the C library (resolv(3)) 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.
On a normally configured system this file should not be necessary. The only name server to be queried will be on the local machine, the
domain name is determined from the host name, and the domain search path is constructed from the domain name.
The different configuration options are:
nameserver
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 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(2); the domain part is taken to be everything
after the first `.'. Finally, if the host name does not contain a domain part, the root domain is assumed.
search Search list for host-name lookup. The search list is normally determined from the local domain name; by default, it begins with the
local domain name, then successive parent domains that have at least two components in their names. This may be changed by listing
the desired domain search path following the search keyword with spaces or tabs separating the names. 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 gen-
erate 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.
The search list is currently limited to six domains with a total of 256 characters.
The domain and search keywords are mutually exclusive. If more than one instance of these keywords is present, the last instance will
override.
The keyword and value must appear on a single line, and the keyword (e.g. nameserver) must start the line. The value follows the keyword,
separated by white space.
FILES
/etc/resolv.conf
SEE ALSO
gethostbyname(3N), resolver(3), hostname(7), named(8)
Name Server Operations Guide for BIND
4th Berkeley Distribution December 14, 1989 RESOLVER(5)