Don't use Google DNS

[leonklingele]

Google DNS (8.8.4.4) is used to e.g. look up the seed nodes.
Why not use a more trustworthy service and stop feeding Google with the number of running nodes and their IP addresses?

Related to monero-project/monero-site#558 which is also using a Google service.

EDIT:
Fix referenced issue.

[moneromooo-monero]

Feel free to suggest a better solution.

Or are you saying it does this by default, rather than be the fallback server when you don't specify one ?

[leonklingele]

monerod could try to use the local resolver first (if available), and use one (multiple?!) from https://wikileaks.org/wiki/Alternative_DNS as a fallback. These might be of interest as well: https://www.reddit.com/r/privacy/comments/43wcg1/non_logging_free_open_dns_without_censorship/
Is kovri also covering DNS given that it supports UDP?

EDIT:
Add more DNS server suggestions.

[moneromooo-monero]

monerod uses the default resolver if you don't specify DNS_PUBLIC. You're saying you don't have DNS_PUBLIC set, your default resolver is not google's, and monerod uses google to resolve ?

AFAIK DNS will go over kovri too.

[moneromooo-monero]

Thanks, that list is useful.

[leonklingele]

Oh, I just noticed I'm defining export DNS_PUBLIC=tcp in my startup script. Commenting out that line "fixes" the issue. The Google IP is hardcoded here:

monero/src/common/dns_utils.cpp

Line 45 in 35d5aa3

#define DEFAULT_DNS_PUBLIC_ADDR "8.8.4.4"

[moneromooo-monero]

You can set DNS_PUBLIC=tcp://x.y.z.a if your local resolver doesn't work well with DNSSEC.

[moneromooo-monero]

#3225

[anonimal]

AFAIK DNS will go over kovri too.

Yes, but only if a DNS server is running a server tunnel and a client tunnel is configured to connect to said server tunnel and the client tunnels DNS requests through said tunnels and only once UDP-related implementations are resolved - but there is no point in using DNS with kovri because the lookup system is completely different.

When we integrate, we'll most likely distribute a hardcoded b32 ledger of nodes to connect to, so name resolution won't be necessary. On the other hand, namecoin is also taking an interest in kovri so something may come up in the works regarding naming solutions. TBD.

[moneromooo-monero]

For updates and checkpoints, since the data is stored in a TXT record in DNS, how would that work then ? You'd change it to a set of known b32 addresses and actually hit the web servers there ?

[anonimal]

For updates and checkpoints, since the data is stored in a TXT record in DNS, how would that work then ?

I could answer this after more time learning monero. Maybe not store in a DNS TXT record? I don't know of an alternate solution at the moment.

You'd change it to a set of known b32 addresses and actually hit the web servers there ?

I'm assuming so. @fluffypony gave an answer to this at some point, I think.

[moneromooo-monero]

+resolved