base node needs 1.1.1.1 to resolve DNS for seednodes if there is no configured seednodes in config

Describe the bug In some places, IP 1.1.1.1 can or has been blocked, breaking the start up of the base node, if there are no seednodes setup in the config file.

To Reproduce Block IP traffic to 1.1.1.1 and start up a fresh run of base node without any seednodes in the config file.

Expected behavior Having a trusted list of failover resolvers before using local or configured resolver would be better.

Also the name_server does not take a plain IP or port address, this needs more info and possible a list of possible trusted records.

[auto_update]
# Name server for auto update (default = "1.1.1.1:53/cloudflare.net")
#name_server = "1.1.1.1:53/cloudflare.net"

# Customize the hosts that are used to check for updates. These hosts must contain update information in DNS TXT
# records. (default = [])
#update_uris = []

#use_dnssec = false

I found this in an older config, but it does not seem to be in the current config.

[peer_seeds]
# DNS seeds hosts - DNS TXT records are queried from these hosts and the resulting peers added to the comms peer list.
#dns_seeds = []
# Custom specified peer seed nodes
#peer_seeds = []
# DNS name server to use for DNS seeds
#dns_seeds_name_server = "1.1.1.1:853/cloudflare-dns.com"
#dns_seeds_name_server = "192.168.0.2:53/leet.lan"
# All DNS seed records must pass DNSSEC validation
#dns_seeds_use_dnssec = false

tari-project / tari

base node needs 1.1.1.1 to resolve DNS for seednodes if there is no configured seednodes in config #6598