Should my private DNS be on or off?

I have a VPS on linode, which runs centos.

I set up postfix and dovecot and configured them for use with my own domain. The domains' DNS is on my private network, and the nameservers are my IP address. The rest of the DNS entries point to Google's DNS servers.

Should I put my DNS entries on Linode's DNS servers, or should I leave them off and use Google's? I'm not using their DNS for my email, just to resolve my domain. I am currently on the free plan, so I'm not too worried about cost. The mail works fine, but I want to make sure it's configured properly.

The nameserver(s) for your domain must be set to the IP address of your VPS. The DNS records for your domain should be set to the IP address of your VPS, and pointed to by the DNS entries for your domain.

If you are concerned about the security of your DNS, you may want to switch the nameservers for your domain to Google's DNS servers. They're pretty good at securing their DNS servers, and it might give you some peace of mind to know that you're not relying on Linode's DNS servers for your domain.

The nameserver(s) for your domain must be set to the IP address of your VPS. Google's DNS is an option, but then I'd need to worry about my public IP. I want to keep the DNS on my private network because it's easier to manage if the changes happen there, and the downtime will only affect me.

I'm not concerned about security at all. My private network is always behind a firewall.

The nameserver(s) for your domain must be set to the IP address of your VPS.

Is 8.8 8.8 a private DNS?

No, it's not a private DNS.

You can't configure the resolvconf to use 8.8 or 8.4 as nameservers, unless you do it yourself manually via editing resolv.conf and /etc/resolv.

I think I need to mention how a domain is created. The company has a domain manager that allows domain owners to change DNS servers. It is through this interface that 8.8 has been setup. I think there might be a problem because when I go to that DNS, I'm not able to ping my local DNS.

When you connect an external DNS to 8.8, what happens is that your external DNS will now become the default for resolving domains. That's why you no longer want the local DNS to resolve the local address of your local computer.

In any case, you can configure resolvconf to do it manually. Just make sure you remove any existing setting from /etc/resolv.d/ and add to /etc/resolv.conf an entry for 8.8 at the end (without any comments, no semicolon at the end) as well as an entry for any additional DNSs that you want to resolve the local hostname with. You need to configure this in resolvconf itself as well, so run dpkg-reconfigure resolvconf and make sure you select the appropriate options.

This is the recommended way to go. The only thing that you need to take into consideration when adding the nameserver is that resolvconf is not smart enough to know what the localhost is and will probably overwrite the settings if you've added a line with "nameserver 127.0.1".

I have done all this and it seems to be working. I can resolve the domain directly using 8.8 as nameserver. However, I still get an error when I try to ping my local DNS. If I then try to ping an external DNS it works fine. So far I'm still able to ping localhost.

I found a solution in Debian Bug #913453 where it says that. Quote: If you are using 8.

Why is my phone saying private DNS server cannot be accessed?

When I try to use some IP addresses for DNS, I get a warning that says "privacy-protected DNS server cannot be accessed".

The thing is, these addresses are valid, and were working just fine on my phone before. I'm also using the same WiFi.

I have to reboot my phone to disable it. I've been searching for answer for the past two days and I can't seem to find anything anywhere. Why is my phone getting these warnings?

DNS is provided by three parties: The DNS Resolver, typically called resolver in Android. The device running the OS. An upstream DNS Server (eg. 8.8 Google public DNS, or 1.1 OpenDNS)

And there are also three ways to use DNS: P2P (Peer-to-peer). WIFI with UPnP. WIFI without UPnP. If you use P2P, DNS queries are sent only between resolvers. The upstream resolvers are never aware of such queries, hence the privacy warning.

In case of WiFi access without UPnP, both upstream DNS Server and resolvers must be configured forwarding to allow sending the P2P queries (see here). Then, depending on your firewall rules, you should be able to reach such server.