the reason you have files in there is cuz if dns is down and you have it in your /etc/hosts it will still resolve. also its always quicker resolveing from /etc/hosts vs dns.
you have to make sure you have the appropriate nameservers specified in the /etc/resolve.conf file.
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)
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)
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)
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)
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)
I have 2 problems. Dhcp is not setting dns and after I manually set my dns it changes to garbage.
I literally just used command to set dns which is a good copy of resolv.conf:
sudo cp /home/bob/Desktop/scripts_9-12-2011/resolv.conf /etc/resolv.confHere is a copy of my resolv.conf.
#... (5 Replies)
I am trying to setup a CentOS 6.2 server that will be doing 3 things DHCP, DNS & Samba for a very small office (2 users). The idea being this will replace a very old Win2k server. The users are all windows based clients so only the server will be Linux based.
I've installed CentOS 6.2 with... (4 Replies)
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
LEARN ABOUT PLAN9
dhcp
dhcp(5) Standards, Environments, and Macros dhcp(5)NAME
dhcp - Dynamic Host Configuration Protocol
DESCRIPTION
Dynamic Host Configuration Protocol (DHCP) enables host systems in a TCP/IP network to be configured automatically for the network as they
boot. DHCP uses a client/server mechanism: servers store configuration information for clients, and provide that information upon a
client's request. The information can include the client's IP address and information about network services available to the client.
This manual page provides a brief summary of the Solaris DHCP implementation.
Solaris DHCP Client
The Solaris DHCP client is implemented as background daemon, dhcpagent(1M). This daemon is started automatically during bootup if there
exists at least one dhcp.interface file in /etc. Only interfaces with a corresponding /etc/dhcp.interface file are automatically configured
during boot. Network parameters needed for system configuration during bootup are extracted from the information recieved by the daemon
through the use of the dhcpinfo(1) command. The daemon's default behavior can be altered by changing the tunables in the /etc/default/dhc-
pagent file. The daemon is controlled by the ifconfig(1M) utility. Check the status of the daemon using the netstat(1M) and ifconfig(1M)
commands.
Solaris DHCP Server
The Solaris DHCP server is implemented as a background daemon, in.dhcpd(1M). This daemon can deliver network configuration information to
either BOOTP or DHCP clients. The Solaris DHCP service can be managed using the dhcpmgr(1M) GUI or the command line utilities dhcpcon-
fig(1M), dhtadm(1M), and pntadm(1M).
DHCP Configuration Tables
The Solaris DHCP server stores client configuration information in the following two types of tables:
dhcptab tables Contain macros and options (also known as symbols), used to construct a package of configuration information to
send to each DHCP client. There exists only one dhcptab for the DHCP service. The dhcptab(4) can be viewed and mod-
ified using the dhtadm(1M) command or dhcpmgr(1M) graphical utility. See dhcptab(4) for more information about the
syntax of dhcptab records. See dhcp_inittab(4) for more information about the DHCP options and symbols.
DHCP network tables DHCP network tables, which contain mappings of client IDs to IP addresses and parameters associated with those
addresses. Network tables are named with the IP address of the network, and can be created, viewed, and modified
using the pntadm command or dhcpmgr graphical utility. See dhcp_network(4) for more information about network
tables.
SEE ALSO dhcpinfo(1), dhcpagent(1M), dhcpconfig(1M), dhcpmgr(1M), dhtadm(1M), ifconfig(1M), in.dhcpd(1M), netstat(1M), pntadm(1M), syslog(3C),
dhcp_network(4), dhcptab(4), dhcpsvc.conf(4), dhcp_inittab(4), dhcp_modules(5)
Solaris DHCP Service Developer's Guide
Alexander, S., and R. Droms. RFC 2132, DHCP Options and BOOTP Vendor Extensions. Silicon Graphics, Inc. Bucknell University. March 1997.
Droms, R. RFC 1534, Interoperation Between DHCP and BOOTP. Bucknell University. October 1993.
Droms, R. RFC 2131, Dynamic Host Configuration Protocol. Bucknell University. March 1997.
Wimer, W. RFC 1542, Clarifications and Extensions for the Bootstrap Protocol. Carnegie Mellon University. October 1993.
SunOS 5.10 13 Mar 2001 dhcp(5)