0

NextDNS Profile and WireGuard Config

Hello,

 

Is there a way I can specify NextDNS in my WireGuard configuration files and still offer protection?

According to https://help.nextdns.io/t/m1hmvag/will-nextdns-filter-content the public IPv4 addresses do not filter anything.

I do not use IPv6 and when I hand out a VPN client config file, I want to make sure a DNS that is actually filtering is configured (otherwise I just specify 1.1.1.3, but that has no malicious filter enabled).

1 reply

null
    • KPL
    • 15 hrs ago
    • Reported - view

    Hi Matthew, I just signed up to the community, hence the 3 week reply time.

    The answer to your question is yes!

    I have done it myself, so I know it works.

     

    Here is a typical  Wireguard Config file:

    [Interface]
    Address = 192.168.7.211/32
    DNS = 1.1.1.1,1.0.0.1
    PrivateKey = QPW1XZ91+MAhOI9J/ic5T+UfBV9G1uMcIHHHPLPP=

    [Peer]
    PublicKey=lHazY+m+QF9mbyMr9vKK+m+I03aAsgMAKopPPLMkP=
    AllowedIPs = 0.0.0.0/0, ::/0
    Endpoint = 185.129.166.52:51820

    ---------

    In the above example, Cloudflare DNS servers are used seperated by a comma.

    All you need do is simply replace your Next DNS servers that are displayed on your Next "Set up" page  under  the Linked IP section.  Note: Your own profile's Next DNS  can be different to another person's profile.

    So here is an example of where I have replaced the Cloudflare DNS with my Next DNS (real number is edited for obvious reasons):

    [Interface]
    Address = 192.168.7.211/32
    DNS =44.95.27.98 ,44.95.29.98
    PrivateKey = QPW1XZ91+MAhOI9J/ic5T+UfBV9G1uMcIHHHPLPP=

    [Peer]
    PublicKey=lHazY+m+QF9mbyMr9vKK+m+I03aAsgMAKopPPLMkP=
    AllowedIPs = 0.0.0.0/0, ::/0
    Endpoint = 185.129.166.52:51820

    Hope this helps.

Login to reply

Content aside

  • 15 hrs agoLast active
  • 1Replies
  • 102Views
  • 2 Following