Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change default DNS servers #975

Conversation

jidckii
Copy link
Contributor

@jidckii jidckii commented Sep 11, 2023

DNS 9.9.9.9 applies filtering based on the VirusTotal database. My domain was included in this database by mistake and I spent several days debugging to understand what was wrong.
2023-09-11_09-40-20

After updating the cluster and the release of the 9.9.9.9 resolver, my sites in the yucca.app domain began to sometimes return http 500, this is because nginx ingress cannot resolve the request on the incoming domain.

2023-09-11_09-32-12
2023-09-11_09-32-29
2023-09-11_09-32-38

I suggest not using the default DNS which uses any filtering and can lead to service failure. The use of such resolvers should be a conscious choice. On its website, quad9 suggests using the address without filtering, so I replaced it in the default variable.

mysticaltech
mysticaltech previously approved these changes Sep 11, 2023
Copy link
Collaborator

@mysticaltech mysticaltech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, makes sense!

@M4t7e
Copy link
Contributor

M4t7e commented Sep 11, 2023

Just my 5 cents:

I was often thinking about the default DNS settings and still I do. Technically all 3 are good and fast, but they have some hidden drawbacks...

  • Cloudflare DNS:
    They openly say that they observe, log and monitor all DNS requests made using their standard DNS resolvers with some level of anonymization. https://www.cloudflare.com/privacypolicy/
  • Google DNS:
    They also observe, log and monitor all DNS requests like Cloudflare. https://developers.google.com/speed/public-dns/faq#privacy
    Additionally they send a so called EDNS-Client-Subnet (ECS) along with the DNS query to the authoritative servers, which simply contains a part of your source IP address.
    Example:
    # dig txt ecs.test.smartguard.io @8.8.8.8 +short
    "128.140.118.0/24"
    # dig txt ecs.test.smartguard.io @2001:4860:4860::8888 +short
    "2a01:4f8:c17:cd00::/56"
    
    # dig txt ecs.test.smartguard.io @1.1.1.1 +short
    "no ECS"
    # dig txt ecs.test.smartguard.io @9.9.9.9 +short
    "no ECS"
  • Quad9:
    The only privacy friendly DNS resolver service and not located in the US (nothing against the US in general, but their laws explicitly ignore EU law, as Edward taught us). But they don't serve all DNS answers uncensored anymore. There is a lawsuit ongoing from Sony Music Entertainment. They claim that Quad9 actively supports people to download music illegally (what a bulls**t). See here for more info: https://www.quad9.net/news/blog/quad9-and-sony-music-german-injunction-update-for-july-2023

TL;DR
I think the Hetzner DNS resolvers may be a better default from a privacy and consistency perspective. Especially because the mixture between Cloudflare, Google and Quad9 can lead to toggle effects in case of some issues like this here. First something works, then it does not work, testing manually and it suddenly works again, and so on...

@jidckii
Copy link
Contributor Author

jidckii commented Sep 11, 2023

I agree with @M4t7e , maybe it makes sense to use resolvers from the hoster?

@mysticaltech
Copy link
Collaborator

Sounds good folks, @jidckii let's default to Hetzner DNS servers then, and cite the current one in the kube.tf.example line to be uncommented if needed.

Copy link
Collaborator

@mysticaltech mysticaltech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jidckii Just two small comments before we move on.

README.md Outdated Show resolved Hide resolved
@jidckii jidckii changed the title Change default DNS 9.9.9.9 to 9.9.9.10 Change default DNS servers Sep 12, 2023
@mysticaltech mysticaltech changed the base branch from master to staging September 12, 2023 19:23
@mysticaltech mysticaltech merged commit 49d0799 into kube-hetzner:staging Sep 12, 2023
1 check passed
@mysticaltech
Copy link
Collaborator

Now live on v2.7.1. thanks again for this @jidckii, and for the great suggestion @M4t7e 👏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants