DataDog NTP

[TPS]

Prerequisites

• I checked the documentation and found no answer;
• I checked to make sure that this issue has not already been filed;
• This is not an ad/bug report.

Problem description

According to DataDog/datadog-agent#1532 (comment), Datadog uses NTP servers as part of their analytics. In my logs, they're of the form #.datadog.pool.ntp.org, where # is currently some low digit (I've recently seen 0-3, but iIrc, perhaps upto 6?).

Proposed solution

I've been running datadog$important for months in both user DNS & content filterlists, & those have never broken anything, but, conservatively |datadog.pool.ntp.org^ should do just this.

Additional information

hagezi/dns-blocklists#4400 includes more pertinent info.

[DandelionSprout]

From personal experience, based on that I run an NTP server that is part of "NTP Pool", blocking an NTP server entirely would have only small bits of tracking to remove (Provided the NTP server is a normally operating one; Something called "DataDog" does sound odd indeed).

There'd normally also be a significant benefits-to-problems tradeoff, but since DataDog doesn't seem to me to be used by specific device brands (whether it be bedroom watches, set-top boxes, etc.), that'd not be a significant factor in this.

The most cautious entry I can come up with would be ||datadog.pool.ntp.org|$dnsrewrite=pool.ntp.org, but I'll let the rest of Team AdGuard give 2nd/3rd/nth Opinions on this.

[Alex-302]

Not sure what can be tracked using this protocol by ntp.org, except public info (IP, region).