10-17-2011
1. Redhat's default ntpd.conf configuration is pure shit. Don't use it. Don't even think about basing your config on it. Notably, remove the "server 127.127...." and fudge lines.
2. You're Windows NT time server is essentially a "tier 2" server. That server (and its mirror/failover) really sohuld be the only "server" lines you need here.
3. You're "restrict" lines may be in fact restricting your server from being modified by the time servers you want to in fact synchronize to. That's how you've set your default, and then you are permissive only with the localhost. So that wouldn't work.
4. If your server is not behnid a firewall which blocks incoming NTP from unknown servers, having the authentication enabled would be a smart idea. Having said that, it might be easier to config the firewall than to figure out ntp's very confusing authentication scheme.
This User Gave Thanks to otheus For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is there a utility which offers the ability to utilize NTP to sync time on machine.
If so please point to man page or web site (3 Replies)
Discussion started by: SmartJuniorUnix
3 Replies
2. AIX
Good morning to all,
can someone advise me how to setup aix ntp server with aix & wintel clients?
Secondly, I also require to enable the service to autostart on reboot, how do I configure this?
Thirdly, how do I configure daily autosync between clients and server?
Please advice, thanks.... (0 Replies)
Discussion started by: chongkls77
0 Replies
3. SuSE
Hi folks,
The server time is no tgetiing synched up with the NTP server.
I tried ntpdate -u <ipadress> this is not working. please help out.
regards,
Sag. (7 Replies)
Discussion started by: sag71155
7 Replies
4. UNIX for Advanced & Expert Users
I need to find out the NTP Clients which are syncing with my NTP Server in a Unix(Linux/Solaris) Machine. For eg. How many Stratum 2 Servers sync the time with my Stratum1 Server. Is there any way to track it?
edit by bakunin: moving the thread to where it belongs: the technical forums. (4 Replies)
Discussion started by: hottyspidy
4 Replies
5. Solaris
Ok, I have 4 production systems. There is one NTP server for all four systems. In each system there is one Solaris 10 box that points to that NTP server. All of the other machines in the system point to the Solaris 10 machine to get their time sync.
All four Solaris 10 machines have essentially... (2 Replies)
Discussion started by: DeCoTwc
2 Replies
6. Linux
All,
I need to write a script which can determine if my NTP client is X second off from the NTPD server time. I am looking for a crafty oneliner to calculate the time difference? (3 Replies)
Discussion started by: vada010
3 Replies
7. Red Hat
Hi,
I have 4 machines and all are NTP configured with same ntp.conf file. But 3 machines are in sync with Time server and 4th machine is not contacting & sync with the NTP server. Please see the below details.
# service ntpd stop
Stopping ntpd: ... (0 Replies)
Discussion started by: uday123
0 Replies
8. HP-UX
Hi
I wonder if its possible to setup NTP clients running HP-UX o.s. from a solaris 10 NTP server?
FR (3 Replies)
Discussion started by: fretagi
3 Replies
9. Solaris
We had a network problem a couple of days before that caused 1 interface to down and up. But today I have noticed that our date is wrong, our system have 4 servers and the other 3 are OK.
I used <date> command, the result is: Fri Jan 2 17:57:55 ICT 1970
I have tried set date to be the same as... (3 Replies)
Discussion started by: salvation3103
3 Replies
10. Red Hat
Hi,
I have two ntp servers in my cluster and I want all the nodes in my cluster to sync with either of the ntp servers or just one. Unfortunately it keep rotating the sync, between my ntp server 1, ntp server 2 and local. Is there anyway I can change the sync to avoid local?
# ntpq -p
... (3 Replies)
Discussion started by: pjeedu2247
3 Replies
LEARN ABOUT ULTRIX
ntp.conf
ntp.conf(5) File Formats Manual ntp.conf(5)
Name
ntp.conf - Network Time Protocol configuration file
Description
The file is the configuration file for the Network Time Protocol (NTP) daemon, This file must be configured on your system before running
Any host names that you specify in the file must have an entry in the file, or an entry in the master database, if the database is being
served to your system by BIND/Hesiod or Yellow Pages.
The file has four entry formats:
trusting no
This entry guarantees that your system synchronizes only to the NTP servers identified in the peer and server entries specified. Dig-
ital recommends that all systems include the entry.
peer server
This entry identifies server as one of the NTP servers that your system trusts, and from which your system will accept time synchro-
nization. Your system may also provide time synchronization to this server. Servers can be identified by host name or internet
address.
NTP servers should be configured with entries.
server server
This entry identifies server as one of the NTP servers that your system trusts, and from which your system will accept time synchro-
nization. Your system can not provide time synchronization to this server. Servers can be identified by host name or internet
address.
NTP clients should be configured with entries.
peer /dev/null LOCL 1 -5 local
This entry identifies your system as a local reference clock. A local reference clock is the most accurate system clock available at
your site. If you receive time synchronization from the Internet NTP service, you should not include this entry on any of your sys-
tems. At most, one system in a set of nodes running should be identified as a local reference clock.
A host which specifies this entry should not specify any or entries.
Examples
This is a sample configuration file for an NTP client which receives time synchronization from the NTP servers: and Lines beginning with a
number sign (#) are comments.
#
# NTP Configuration File
# This file is mandatory for the ntpd daemon
#
#
#
# ** A L L **
#
# "trusting no" prevents this host from synchronizing
# to any host that is not listed below. It is recommended
# that all hosts include the line "trusting no".
#
trusting no
#
#
# ** S E R V E R **
#
# If you are configuring a server, use "peer" entries to
# synchronize to other NTP servers. For example, server1,
# server2, and server3.
#
#peer server1
#peer server2
#peer server3
#
#
#
#
# ** C L I E N T **
#
# If you are configuring a client, use "server" entries to
# synchronize to NTP servers. For example, server1, server2,
# and server3.
#
server server1
server server2
server server3
#
#
#
# ** L O C A L R E F E R E N C E C L O C K **
#
# If you are configuring a local reference clock, include the
# following entry and the "trusting no" entry ONLY.
#
#peer /dev/null LOCL 1 -5 local
#
See Also
ntp(1), ntpd(8), ntpdc(8)
RFC 1129--Internet time synchronization: The Network Time Protocol
Introduction to Networking and Distributed System Services
ntp.conf(5)