Skip to main content
Indicate that this isn't my preferred answer
Source Link
mpboden
  • 1.7k
  • 1
  • 5
  • 21

UPDATE

This is no longer my preferred answer. I've added another answer here.


UPDATE

This is no longer my preferred answer. I've added another answer here.


update dig command to use tls for final test
Source Link
mpboden
  • 1.7k
  • 1
  • 5
  • 21

Finally, if you do a DNS query with dig +tls google.com, you should see one of your defined nameservers being used and not the stub resolver or your local uplink server. And if it all goes well, it should be using DNS-over-TLS through your VPN.

Finally, if you do a DNS query with dig, you should see one of your defined nameservers being used and not the stub resolver or your local uplink server. And if it all goes well, it should be using DNS-over-TLS through your VPN.

Finally, if you do a DNS query with dig +tls google.com, you should see one of your defined nameservers being used and not the stub resolver or your local uplink server. And if it all goes well, it should be using DNS-over-TLS through your VPN.

fixed typo mistake
Source Link
mpboden
  • 1.7k
  • 1
  • 5
  • 21
# This is the network config written by 'subiquity'
network:
  ethernets:
    enp0s10:
      dhcp4: true
      dhcpdhcp4-overrides:
        use-dns: false
  version: 2
# This is the network config written by 'subiquity'
network:
  ethernets:
    enp0s10:
      dhcp4: true
      dhcp-overrides:
        use-dns: false
  version: 2
# This is the network config written by 'subiquity'
network:
  ethernets:
    enp0s10:
      dhcp4: true
      dhcp4-overrides:
        use-dns: false
  version: 2
Post Undeleted by mpboden
added 2789 characters in body
Source Link
mpboden
  • 1.7k
  • 1
  • 5
  • 21
Loading
Post Deleted by mpboden
Source Link
mpboden
  • 1.7k
  • 1
  • 5
  • 21
Loading