10-22-2003
if you have a small network (~4 systems) you might as well just add them to your /etc/hosts file. however, if you already have a private DNS server running on your internal network, then yeah add everything in there. that helps to keep consistency in your network and you wont have to worry about one /etc/hosts being outdated.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
This is more of a verification rather than a question of technical nature.
This is based on solaris 10 machine
Could we use Virtual hosts (within our hosts file):
123.1.1.10 virtual_host_name
123.1.1.10 host_A
(note: 123.1.1.10 - host_A is also in our DNS server entry)
And... (0 Replies)
Discussion started by: jackola
0 Replies
2. Solaris
Hi all
Is there any reason to have "hosts ldap dns" as line in /etc/nsswitch.conf ? My understanding is that ldap does not contain any host information..(?)
Best regards...Ludwig (1 Reply)
Discussion started by: ludwig
1 Replies
3. Solaris
As i understand, host/nslookup/dig only query DNS server to resolve name to ip.
ping can query both, but it seems if ping is blocked, ping won't return IP.
traceroute can query both, but i am not able to test if traceroute is blocked, What is the result?
Neither ping/traceroute is... (3 Replies)
Discussion started by: honglus
3 Replies
4. IP Networking
Hi all,
I have an entry in my hosts file on a server called tractor as follows:
10.67.34.128 digger-m2m digger
I have a DNS server configured but it doesn't seem to know about digger. When I do an nslookup on tractor for digger i get the following:
new_dns1.oam.uk can't find digger: Non... (0 Replies)
Discussion started by: Donkey25
0 Replies
5. AIX
hi all
just installed the netsec.options.tcpwrapper from expansion pack, which used to be a rpm, for my aix 6.1 test box.
it is so unpredictable. i set up the hosts.deny as suggested for all and allow the sshd for specific ip addresses/hostnames.
the tcpdchk says the hosts allowed and... (0 Replies)
Discussion started by: wf201626
0 Replies
6. IP Networking
Old skool UNIX and Linux geek here, but newbie to the world of DNS and bind. I've recently been tasked with replacing our DNS infrastructure, currently on Windows, with a RHEL based solution. And I assume that means using bind, which I've not used before. Here's my question:
Suppose our company... (3 Replies)
Discussion started by: lupin..the..3rd
3 Replies
7. 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
8. AIX
Hello,
For what purpose /etc/hosts file is used.I mean how any request coming to a DNS server or a switch would know that which name and ip are configured in /etc/hosts files of a server?
Best regards,
Vishal (3 Replies)
Discussion started by: admin_db
3 Replies
9. AIX
Hello guys,
I am new to AIX .
I have two AIX v5.3 servers running BIND DNS service on them. The plan is to shut down only the DNS service on them, but in order to do that I have to determine which internal hosts are still using the servers to resolve DNS queries.
Can you please advice on... (2 Replies)
Discussion started by: tihomirvs
2 Replies
10. Solaris
Am trying to copy a tar file onto a series of remote hosts and untar it at the destination. Need to do this without having to do multiple ssh.
Actions to perform within a single ssh session via shell script
- copy a file
- untar at destination (remote host)
OS : Linux RHEL6 (3 Replies)
Discussion started by: sankasu
3 Replies
HOSTS(5) Linux Programmer's Manual HOSTS(5)
NAME
hosts - The static table lookup for hostnames
SYNOPSIS
/etc/hosts
DESCRIPTION
This manual page describes the format of the /etc/hosts file. This file is a simple text file that associates IP addresses with hostnames,
one line per IP address. For each host a single line should be present with the following information:
IP_address canonical_hostname [aliases...]
Fields of the entry are separated by any number of blanks and/or tab characters. Text from a "#" character until the end of the line is a
comment, and is ignored. Host names may contain only alphanumeric characters, minus signs ("-"), and periods ("."). They must begin with
an alphabetic character and end with an alphanumeric character. Optional aliases provide for name changes, alternate spellings, shorter
hostnames, or generic hostnames (for example, localhost).
The Berkeley Internet Name Domain (BIND) Server implements the Internet name server for Unix systems. It augments or replaces the
/etc/hosts file or hostname lookup, and frees a host from relying on /etc/hosts being up to date and complete.
In modern systems, even though the host table has been superseded by DNS, it is still widely used for:
bootstrapping
Most systems have a small host table containing the name and address information for important hosts on the local network. This is
useful when DNS is not running, for example during system bootup.
NIS Sites that use NIS use the host table as input to the NIS host database. Even though NIS can be used with DNS, most NIS sites still
use the host table with an entry for all local hosts as a backup.
isolated nodes
Very small sites that are isolated from the network use the host table instead of DNS. If the local information rarely changes, and
the network is not connected to the Internet, DNS offers little advantage.
FILES
/etc/hosts
NOTES
Modifications to this file normally take effect immediately, except in cases where the file is cached by applications.
Historical Notes
RFC 952 gave the original format for the host table, though it has since changed.
Before the advent of DNS, the host table was the only way of resolving hostnames on the fledgling Internet. Indeed, this file could be
created from the official host data base maintained at the Network Information Control Center (NIC), though local changes were often
required to bring it up to date regarding unofficial aliases and/or unknown hosts. The NIC no longer maintains the hosts.txt files, though
looking around at the time of writing (circa 2000), there are historical hosts.txt files on the WWW. I just found three, from 92, 94, and
95.
EXAMPLE
127.0.0.1 localhost
192.168.1.10 foo.mydomain.org foo
192.168.1.13 bar.mydomain.org bar
146.82.138.7 master.debian.org master
209.237.226.90 www.opensource.org
SEE ALSO
hostname(1), resolver(3), resolver(5), hostname(7), named(8), Internet RFC 952
COLOPHON
This page is part of release 3.25 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 2002-06-16 HOSTS(5)