HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
home-assistant
plugin-dns
Go2021–2021
home-assistant / plugin-dns

plugin-dns

CoreDNS implementation for Home Assistant

3Distinct people
5Mentions
0Explicit recommenders
23GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

CoreDNS implementation for Home Assistant

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day5 dated mentions

Observed mentions: 2021-10-03 20:09:42 UTC to 2021-10-12 06:00:25 UTC.

012021-10-03 00:00:00 UTC to 2021-10-04 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsOct 32021-10-04 00:00:00 UTC to 2021-10-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-10-05 00:00:00 UTC to 2021-10-06 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2021-10-06 00:00:00 UTC to 2021-10-07 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-10-07 00:00:00 UTC to 2021-10-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsOct 72021-10-08 00:00:00 UTC to 2021-10-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-10-09 00:00:00 UTC to 2021-10-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-10-10 00:00:00 UTC to 2021-10-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-10-11 00:00:00 UTC to 2021-10-12 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-10-12 00:00:00 UTC to 2021-10-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 12

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 32021-10-03 00:00:00 UTC2021-10-04 00:00:00 UTC110
Oct 42021-10-04 00:00:00 UTC2021-10-05 00:00:00 UTC000
Oct 52021-10-05 00:00:00 UTC2021-10-06 00:00:00 UTC110
Oct 62021-10-06 00:00:00 UTC2021-10-07 00:00:00 UTC101
Oct 72021-10-07 00:00:00 UTC2021-10-08 00:00:00 UTC000
Oct 82021-10-08 00:00:00 UTC2021-10-09 00:00:00 UTC000
Oct 92021-10-09 00:00:00 UTC2021-10-10 00:00:00 UTC000
Oct 102021-10-10 00:00:00 UTC2021-10-11 00:00:00 UTC000
Oct 112021-10-11 00:00:00 UTC2021-10-12 00:00:00 UTC101
Oct 122021-10-12 00:00:00 UTC2021-10-13 00:00:00 UTC101

What Hacker News says

5 sources
Unfortunately, I don't think the maintainers are actually open to contributions. See: - https://github.com/home-assistant/plugin-dns/pull/56 - https://github.com/home-assistant/plugin-dns/pull/59 - https://github.com/home-assistant/plugin-dns/pull/61 Almost every question I asked was either ignored or got a response of "that is off topic". I gave up trying to write the PR, which was clearly what the maintainers wanted. There are also bugs in the coredns config that are being ignored: - https://github.com/home-assistant/plugin-dns/pull/55 - https://github.com/home-assistant/plugin-dns/pull/60
In Home Assistant uses hard coded DNS servers
https://github.com/home-assistant/plugin-dns/issues/22 seems to cover the arguments and I see it ends with the software maintainers writing "We are open to contributions that adds features to improve this". The discussion has since been carried to reddit and now HN. GDPR violation might be happening here. I think it will be hard to convince a local regulartory body to act. The software itself isn't collecting/storing and I think one needs to argue first if Cloudflare's data protection is not suffienct enough. As I understand doing a quick read "Your DNS Resolver Information is anonymized at our [Cloudflare's] edge data centers.". If it's always edge data centers it's not clear if data is leaving the EU, etc.
In Home Assistant uses hard coded DNS servers
> I think it is configurable though? Just edit the source file you linked to on your system disk. Unfortunately it is not :(. The change will get wiped any time HA is restarted. > If the internet is not working (because general connectivity is lost, or someone blocked the DNS server, whatever) then of course the internet-using parts will cease to work, but local network parts should still be working. Local network parts stop working as well. A DNS lookup for a non-existing local domain results in the query being sent to Cloudflare. This cannot be prevented. > The config file is pretty clear that it is not supposed to use DNS servers, cloudfare or any other ones, for the local network connections. If this is not the case, you should file a bug. Many bug reports have been filed about this: https://github.com/home-assistant/plugin-dns/issues
Read the rest
. If you look at the config file, SERVFAIL and NXDOMAIN responses are considered to be a "failure" and queries are sent to Cloudflare. This is a poor design decision, not a bug.
In Home Assistant uses hard coded DNS servers

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.