Mario Iseli schreef: > It was simply necessary to write the following to the config: > "ntp server 192.168.16.29"... So, if the router could resolve DNS and > would have access to the Internet you could also add something in the > form of ...pool.ntp.org :) > IOS can do DNS resolving (when you have configured one or more DNS servers) but unfortunately, when you type:
ntp server pool.ntp.org it will resolve the DNS entry at that moment, and write the resulting IP address into config. This is a NO-NO because you will lose NTP sync forever when that server goes away. (ntpd at least does the resolve at every restart but even that is not really optimal, as discussed before) So, when you want your cisco to be a server in the pool, I think it is best to not use other pool members as the reference. Use a couple of the known available timeservers (if necessary with their agreement) as a reference instead. You should not configure "ntp peer". It is not necessary for your router to become a server, and the implementation of NTP peers in IOS does not work very well. (the NTP in IOS is very old code and apparently not an item that receives lots of maintenance attention) Rob _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
