01-31-2012
If you only have 2 uses why not just safe your self some trouble with DNS and just use the /etc/hosts file?
10 More Discussions You Might Find Interesting
1. IP Networking
I have just started learning Unix on Solaris and have been asked to learn DHCP, DNS and LDAP very quick in order to implement them and maintain.
Does anyone know how to do this or a decent book that will include all the above three which tells you how to install and maintain. All i have found so... (2 Replies)
Discussion started by: ollyparkhouse
2 Replies
2. IP Networking
I have managed to setup my Solaris box to receive an IP number from a DHCP server. In addition, I can ping and telnet between my dhcp server and my solaris box using the IP number. However, I can't resolve addresses by name from my solaris box.
In my nsswitch.conf file I have:
hosts: dns
... (4 Replies)
Discussion started by: marist89
4 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
I'm in the dark about this. I have setup a dhcp server and a DNS server. I'm confuss as to how to have DNS auto update any new clinet that the dhcp has given an ip address for. Can this be done. I think that I'm missing something in the configuration of DHCP. I was told that when a DHCPD... (3 Replies)
Discussion started by: larry
3 Replies
4. IP Networking
I asked a similar type question in the solaris forum but i think this relates closer to networking. I am trying to setup a small NIS environment that is contained within a large company network. The client machines are getting an IP from the companys' Windows DHCP server. The NIS server has a... (3 Replies)
Discussion started by: meyersp
3 Replies
5. Solaris
I'm running Solaris 9 and I need my box to request it's DNS servers off a DHCP server - can I do this? (1 Reply)
Discussion started by: Jdogg
1 Replies
6. IP Networking
I'm not sure it that's the right term for what I'm asking about, but it's the best I could come up with. Here is my situation...
I'm setting up a network using OpenVPN. The clients I'm setting up will need to be able to access their own DNS servers (to resolve internal names at their location)... (4 Replies)
Discussion started by: deckard
4 Replies
7. IP Networking
hello
i am running my sipx server in 192.168.2.14
i would like to configure domain name and host name for this .....
can anyone tell me how to configure dns server and dhcp server so that any body both outside and inside the lan could access the sipx server by their host.domain.com name (1 Reply)
Discussion started by: sudeepiit
1 Replies
8. UNIX for Dummies Questions & Answers
Hi to all.
Sorry for my bad english.
For pure self-educational, not professional, purposes, I am studying how to configure a server with several services operating on it.
For my experiment I'm using VirtualBox 3.1.4 on a WinXP host with 3 FreeBSD guests; one acts as a DHCP + DNS server; the... (0 Replies)
Discussion started by: marboxer
0 Replies
9. UNIX for Advanced & Expert Users
Is dnsmasq important for dhcp to setup dns? (3 Replies)
Discussion started by: cokedude
3 Replies
10. IP Networking
Let's say I have a home network containing a server that acts as the resident gateway and serves dhcp and dns requests. Laptop A is frequently connected and disconnected from the network as it is used as a travel computer. Is there a secure way to make sure that whenever laptop A is connected to... (3 Replies)
Discussion started by: Zygomorph
3 Replies
HOSTS(5) Linux Programmer's Manual HOSTS(5)
NAME
hosts - 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.53 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)