惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

aimingoo的专栏
aimingoo的专栏
宝玉的分享
宝玉的分享
J
Java Code Geeks
Martin Fowler
Martin Fowler
博客园 - Franky
I
InfoQ
Stack Overflow Blog
Stack Overflow Blog
Blog — PlanetScale
Blog — PlanetScale
S
SegmentFault 最新的问题
B
Blog
The Cloudflare Blog
F
Fortinet All Blogs
量子位
腾讯CDC
博客园 - 司徒正美
D
Docker
大猫的无限游戏
大猫的无限游戏
Microsoft Azure Blog
Microsoft Azure Blog
T
The Blog of Author Tim Ferriss
V
Visual Studio Blog
IT之家
IT之家
Last Week in AI
Last Week in AI
D
DataBreaches.Net
小众软件
小众软件

Plugin on CoreDNS: DNS and Service Discovery

kubernetes log proxyproto rewrite forward clouddns errors grpc_server https https3 docker auto geoip multisocket nomad dnstap import ready etcd header loadbalance bind grpc file prometheus quic kubeforward JSON gslb autopath
warnlist
2021-06-03 · via Plugin on CoreDNS: DNS and Service Discovery

Description

The warnlist plugin accepts a list of malicious or otherwise undesirable domains and emits a log entry and Prometheus metrics when a domain (or subdomain) is requested.

Prohibited domains can be loaded from a local file or a URL and can be automatically reloaded after a specified period.

warnlist can be thought of as a non-blocking blacklist/blocklist/denylist/badlist. When used with a curated data source, the plugin can surface simplistic low-noise alerts without the need to ship and inspect DNS logs.

Refer to the project README for more info.

An unofficial coredns image with this plugin already compiled is hosted by Giant Swarm on Quay and Docker Hub, as [quay.io/]giantswarm/coredns-warnlist-plugin.

Syntax

warnlist {
    <source type> <source path> <file format>
    reload <reload period>
    match_subdomains <true | false>
}

The warnlist plugin accepts the following arguments:

  • <source type>: Type of the domain list. Either url or file.
  • <source path>: Where to load the list from. Either a URL or file path.
  • <file format>: Format of the file to expect. Either hostfile or text.
  • <reload period>: (Optional) Go Duration after which the list will be regenerated*.
  • <match subdomains>: (Optional) If true (default), the plugin will also check and match subdomains of those explicitly listed. Either true or false.

* A jitter of +/- 30% is automatically added. When automatically reloading from a URL, please be friendly to the service hosting the file.

Example

Sample Corefile using a URL data source, reloading every ~60 minutes:

. {
    log
    warnlist {
        url https://urlhaus.abuse.ch/downloads/hostfile/ hostfile
        reload 60m
    }
    prometheus
    forward . /etc/resolv.conf
}

Metrics

If the prometheus plugin is also enabled, this plugin emits the following metrics:

  • warnlist_hits_total{server, requestor, domain} - counts the number of warnlisted domains requested. The host and domain are included as labels.
  • warnlist_failed_reloads_count{server} - counts the number of times the plugin has failed to reload.
  • warnlist_cache_check_duration_seconds{server} - summary for determining the average time it takes to check the warnlist.
  • warnlist_warnlisted_items_count{server} - current number of domains stored in the warnlist.