Displaying 4 results from an estimated 4 matches for "ntp_server_misuse_and_abus".
Did you mean:
ntp_server_misuse_and_abuse
2016 Jun 08
2
unbound and ntp issuse
Slawa Olhovchenkov <slw at zxy.spb.ru> writes:
> IMHO, ntp.conf need to include some numeric IP of public ntp servers.
https://en.wikipedia.org/wiki/NTP_server_misuse_and_abuse
https://en.wikipedia.org/wiki/Poul-Henning_Kamp#Dispute_with_D-Link
DES
--
Dag-Erling Sm?rgrav - des at des.no
2016 Jun 08
2
unbound and ntp issuse
Slawa Olhovchenkov <slw at zxy.spb.ru> writes:
> IMHO, ntp.conf need to include some numeric IP of public ntp servers.
https://en.wikipedia.org/wiki/NTP_server_misuse_and_abuse
https://en.wikipedia.org/wiki/Poul-Henning_Kamp#Dispute_with_D-Link
DES
--
Dag-Erling Sm?rgrav - des at des.no
2016 Jun 02
2
unbound and ntp issuse
Default install with local_unbound and ntpd can't be functional with
incorrect date/time in BIOS:
Unbound requred correct time for DNSSEC check and refuseing queries
("Jul 1 20:17:29 yellowrat unbound: [3444:0] info: failed to prime trust anchor -- DNSKEY rrset is not secure . DNSKEY IN")
ntpd don't have any numeric IP of ntp servers in ntp.conf -- only
symbolic names like
2016 Jun 02
2
unbound and ntp issuse
Default install with local_unbound and ntpd can't be functional with
incorrect date/time in BIOS:
Unbound requred correct time for DNSSEC check and refuseing queries
("Jul 1 20:17:29 yellowrat unbound: [3444:0] info: failed to prime trust anchor -- DNSKEY rrset is not secure . DNSKEY IN")
ntpd don't have any numeric IP of ntp servers in ntp.conf -- only
symbolic names like