Sponsored Content
Operating Systems Linux NTPD seems to be not syncing !!! Post 94775 by csaha on Tuesday 3rd of January 2006 11:55:07 PM
Old 01-04-2006
Hi Friend

Quote:
I did not find the first site on the lists. The second site is a stratum 1. I would just use the second entry. If you use multiple servers, you need at least 3. Two servers does not work very well.
which site are you talking about ? I am able so get response from all the websites/links/ip adresses given here.

See below ===

Quote:
C:\Documents and Settings\csaha>ping billthecat.sdsc.edu

Pinging billthecat.sdsc.edu [132.249.20.60] with 32 bytes of data:

Reply from 132.249.20.60: bytes=32 time=315ms TTL=232
Reply from 132.249.20.60: bytes=32 time=306ms TTL=232
Reply from 132.249.20.60: bytes=32 time=332ms TTL=232
Reply from 132.249.20.60: bytes=32 time=319ms TTL=232

Ping statistics for 132.249.20.60:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 306ms, Maximum = 332ms, Average = 318ms

C:\Documents and Settings\csaha>ping clock.isc.org

Pinging clock.isc.org [204.152.184.72] with 32 bytes of data:

Reply from 204.152.184.72: bytes=32 time=312ms TTL=42
Reply from 204.152.184.72: bytes=32 time=304ms TTL=42
Reply from 204.152.184.72: bytes=32 time=304ms TTL=42
Reply from 204.152.184.72: bytes=32 time=301ms TTL=42

Ping statistics for 204.152.184.72:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 301ms, Maximum = 312ms, Average = 305ms
 

5 More Discussions You Might Find Interesting

1. HP-UX

Ntpd

Hello, I'm looking for assitance on setting up network time protocol on my HP-ux boxes. I have edit the .conf file accordingly. And /etc/services. But whenever I try and start the service nothing happens at all. No error message, nothing. I have a SCO box as a time server and I wish... (0 Replies)
Discussion started by: satinet
0 Replies

2. AIX

ntpd version

How to check the ntpd version of AIX 5.3 ? (3 Replies)
Discussion started by: alanlkw
3 Replies

3. Shell Programming and Scripting

Modifying the ntpd deamon script

I need to replace the line daemon ntpd $OPTIONS in the following script with daemon ntpd $OPTIONS 2>&1 > /var/log/ntpd.log & what will happen? The idea of replacing is to capture the output on the console into ntpd.log file. Will this work? ... (1 Reply)
Discussion started by: naive1977
1 Replies

4. Red Hat

ntpd -gq not working

as advised and documented, i'm trying to use the ntpd -gq instead of ntpdate. The result is that clock not set. as below. However ntpdate is working ok and had set the clock correctly this is the ntp.conf file: # cat /etc/ntp.conf logfile /var/log/ntp.log driftfile /var/lib/ntp/drift... (6 Replies)
Discussion started by: ahmad.zuhd
6 Replies

5. Debian

Ntpd slow start

on every boot, ntpd takes long time to start (after moving from dhcp to static ip). is there a way to speed it up? (1 Reply)
Discussion started by: orange47
1 Replies
DNSSEC-COVERAGE(8)						       BIND9							DNSSEC-COVERAGE(8)

NAME
dnssec-coverage - checks future DNSKEY coverage for a zone SYNOPSIS
dnssec-coverage [-K directory] [-f file] [-d DNSKEY TTL] [-m max TTL] [-r interval] [-c compilezone path] [zone] DESCRIPTION
dnssec-coverage verifies that the DNSSEC keys for a given zone or a set of zones have timing metadata set properly to ensure no future lapses in DNSSEC coverage. If zone is specified, then keys found in the key repository matching that zone are scanned, and an ordered list is generated of the events scheduled for that key (i.e., publication, activation, inactivation, deletion). The list of events is walked in order of occurrence. Warnings are generated if any event is scheduled which could cause the zone to enter a state in which validation failures might occur: for example, if the number of published or active keys for a given algorithm drops to zero, or if a key is deleted from the zone too soon after a new key is rolled, and cached data signed by the prior key has not had time to expire from resolver caches. If zone is not specified, then all keys in the key repository will be scanned, and all zones for which there are keys will be analyzed. (Note: This method of reporting is only accurate if all the zones that have keys in a given repository share the same TTL parameters.) OPTIONS
-f file If a file is specified, then the zone is read from that file; the largest TTL and the DNSKEY TTL are determined directly from the zone data, and the -m and -d options do not need to be specified on the command line. -K directory Sets the directory in which keys can be found. Defaults to the current working directory. -m maximum TTL Sets the value to be used as the maximum TTL for the zone or zones being analyzed when determining whether there is a possibility of validation failure. When a zone-signing key is deactivated, there must be enough time for the record in the zone with the longest TTL to have expired from resolver caches before that key can be purged from the DNSKEY RRset. If that condition does not apply, a warning will be generated. The length of the TTL can be set in seconds, or in larger units of time by adding a suffix: 'mi' for minutes, 'h' for hours, 'd' for days, 'w' for weeks, 'mo' for months, 'y' for years. This option is mandatory unless the -f has been used to specify a zone file. (If -f has been specified, this option may still be used; it will overrde the value found in the file.) -d DNSKEY TTL Sets the value to be used as the DNSKEY TTL for the zone or zones being analyzed when determining whether there is a possibility of validation failure. When a key is rolled (that is, replaced with a new key), there must be enough time for the old DNSKEY RRset to have expired from resolver caches before the new key is activated and begins generating signatures. If that condition does not apply, a warning will be generated. The length of the TTL can be set in seconds, or in larger units of time by adding a suffix: 'mi' for minutes, 'h' for hours, 'd' for days, 'w' for weeks, 'mo' for months, 'y' for years. This option is mandatory unless the -f has been used to specify a zone file, or a default key TTL was set with the -L to dnssec-keygen. (If either of those is true, this option may still be used; it will overrde the value found in the zone or key file.) -r resign interval Sets the value to be used as the resign interval for the zone or zones being analyzed when determining whether there is a possibility of validation failure. This value defaults to 22.5 days, which is also the default in named. However, if it has been changed by the sig-validity-interval option in named.conf, then it should also be changed here. The length of the interval can be set in seconds, or in larger units of time by adding a suffix: 'mi' for minutes, 'h' for hours, 'd' for days, 'w' for weeks, 'mo' for months, 'y' for years. -c compilezone path Specifies a path to a named-compilezone binary. Used for testing. SEE ALSO
dnssec-checkds(8), dnssec-dsfromkey(8), dnssec-keygen(8), dnssec-signzone(8) AUTHOR
Internet Systems Consortium COPYRIGHT
Copyright (C) 2013 Internet Systems Consortium, Inc. ("ISC") BIND9 April 16, 2012 DNSSEC-COVERAGE(8)
All times are GMT -4. The time now is 07:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy