Sponsored Content
Full Discussion: dns and hosts file
Special Forums IP Networking dns and hosts file Post 42104 by rmuhammad on Wednesday 22nd of October 2003 09:27:57 AM
Old 10-22-2003
Question dns and hosts file

ok i have a question now when i add machines on network that are running unix do i add them in the /etc/hosts file also include them in dns
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Virtual Hosts and Alteon DNS conflicts

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

/etc/nsswitch.conf hosts ldap dns

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

Which lookup tool query both hosts and DNS server?

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

Hosts file ignored, no DNS entry but still routes!!

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

aix tcp wrappers hosts.allow hosts.deny?

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

Newbie BIND DNS question: resolving upstream hosts?

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

IPtable rules for DNS/http/https traffic for specific hosts only, not working.

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

Use of /etc/hosts files in resolving the dns name

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

How to find which internal hosts still using my DNS service ? Please help

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

How to copy a tar file on a series of remote hosts and untar it on those hosts?

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
TIMED(8)						    BSD System Manager's Manual 						  TIMED(8)

NAME
timed -- time server daemon SYNOPSIS
timed [-dMt] [-F host ...] [-G netgroup] [-i network | -n network] DESCRIPTION
The timed utility is a time server daemon which is normally invoked at boot time from the rc(8) file. It synchronizes the host's time with the time of other machines, which are also running timed, in a local area network. These time servers will slow down the clocks of some machines and speed up the clocks of others to bring them to the average network time. The average network time is computed from measurements of clock differences using the ICMP timestamp request message. The following options are available: -d Enable debugging mode; do not detach from the terminal. -F host ... Create a list of trusted hosts. The timed utility will only accept trusted hosts as masters. If it finds an untrusted host claiming to be master, timed will suppress incoming messages from that host and call for a new election. This option implies the -M option. If this option is not specified, all hosts on the connected networks are treated as trustworthy. -G netgroup Specify a netgroup of trustworthy hosts, in addition to any masters specified with the -M flag. This option may only be specified once. -i network Add network to the list of networks to ignore. All other networks to which the machine is directly connected are used by timed. This option may be specified multiple times to add more than one network to the list. -M Allow this host to become a timed master if necessary. -n network Add network to the list of allowed networks. All other networks to which the machine is directly connected are ignored by timed. This option may be specified multiple times to add more than one network to the list. -t Enable tracing of received messages and log to the file /var/log/timed.log. Tracing can be turned on or off while timed is running with the timedc(8) utility. The -n and -i flags are mutually exclusive and require as arguments real networks to which the host is connected (see networks(5)). If nei- ther flag is specified, timed will listen on all connected networks. A timed running without the -M nor -F flags will always remain a slave. If the -F flag is not used, timed will treat all machines as trust- worthy. The timed utility is based on a master-slave scheme. When timed is started on a machine, it asks the master for the network time and sets the host's clock to that time. After that, it accepts synchronization messages periodically sent by the master and calls adjtime(2) to per- form the needed corrections on the host's clock. It also communicates with date(1) in order to set the date globally, and with timedc(8), a timed control utility. If the machine running the master becomes unreachable, the slaves will elect a new master from among those slaves which are running with at least one of the -M and -F flags. At startup timed normally checks for a master time server on each network to which it is connected, except as modified by the -n and -i options described above. It will request synchronization service from the first master server located. If permitted by the -M or -F flags, it will provide synchronization service on any attached networks on which no trusted master server was detected. Such a server propagates the time computed by the top-level master. The timed utility will periodically check for the presence of a master on those networks for which it is operating as a slave. If it finds that there are no trusted masters on a network, it will begin the election process on that network. One way to synchronize a group of machines is to use ntpd(8) to synchronize the clock of one machine to a distant standard or a radio receiver and -F hostname to tell its timed to trust only itself. Messages printed by the kernel on the system console occur with interrupts disabled. This means that the clock stops while they are print- ing. A machine with many disk or network hardware problems and consequent messages cannot keep good time by itself. Each message typically causes the clock to lose a dozen milliseconds. A time daemon can correct the result. Messages in the system log about machines that failed to respond usually indicate machines that crashed or were turned off. Complaints about machines that failed to respond to initial time settings are often associated with ``multi-homed'' machines that looked for time masters on more than one network and eventually chose to become a slave on the other network. WARNINGS
Temporal chaos will result if two or more time daemons attempt to adjust the same clock. If both timed and another time daemon are run on the same machine, ensure that the -F flag is used, so that timed never attempts to adjust the local clock. The protocol is based on UDP/IP broadcasts. All machines within the range of a broadcast that are using the TSP protocol must cooperate. There cannot be more than a single administrative domain using the -F flag among all machines reached by a broadcast packet. Failure to fol- low this rule is usually indicated by complaints concerning ``untrusted'' machines in the system log. FILES
/var/log/timed.log tracing file for timed /var/log/timed.masterlog log file for master timed SEE ALSO
date(1), adjtime(2), gettimeofday(2), icmp(4), netgroup(5), networks(5), ntpd(8), timedc(8) R. Gusella and S. Zatti, TSP: The Time Synchronization Protocol for UNIX 4.3BSD. HISTORY
The timed utility appeared in 4.3BSD. BSD
May 11, 1993 BSD
All times are GMT -4. The time now is 12:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy