WireGuard, full power with Cloudflare WARP and NextDNS

Update Jul, 11th 2022

I no longer recommend using 53 listening port in configuration profiles. I suggest to use 443 port. Also, on mobile devices, it appears that changing port to 443 and removing MTU line from configuration profiles make the connection more reliable. So, use 443 port for ListenPort field and remove MTU field.

You can skip all the prior explainations and go to the tutorial by clicking here.


Whoever you are reading this, you probably already felt concerned about whether your Internet browsing was safe from unwelcome eyes… or ears.

The topic of today’s post is the Wireguard® VPN protocol and how to completely browse the Web without worrying about your privacy, for free thanks to Cloudflare WARP VPN, NextDNS DNS service, and WGCF tool.


WireGuard® is an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. It aims to be faster, simpler, leaner, and more useful than IPsec, while avoiding the massive headache. It intends to be considerably more performant than OpenVPN.
— WireGuard

I can’t explain it better than that.

Cloudflare WARP

Cloudflare WARP1 is a cross-platform VPN, designed to be free and fast, using DNS servers combined with WARP application to provide a secure connection using Cloudflare infrastructure. The DNS service is claimed by Cloudflare to be the fastest DNS service around there. They state that they don’t log your IP address and don’t know whatever you’re doing on Internet. WARP is a software that redirects all the traffic from your device to the Cloudflare network, not just DNS traffic. WARP uses BoringTun3 which consists of a userspace WireGuard implementation.

However, WARP is not a kind of flexible VPN. You can’t change your location. You have no control over your outbound IP address and Cloudflare does not even guarantee that your IP address will be different from the requested website point-of-view. The IP address it will see when you’ll be visiting it may be the same as your real IP address. So, don’t expect to virtually travel around the world, you won’t be circumventing RTBF restrictions to watch Formula 1 Grand Prix from France.


NextDNS is a freemium DNS service that provides a secure DNS resolution that can be set to block domain lists (like ads-related ones) and that can provide on-demand analytics. NextDNS is free until you reach your monthly quota of 300,000 DNS requests. You can pay for unlimited DNS requests.

Why using NextDNS in place of is a great and fast DNS service but it differs from NextDNS in some ways: and NextDNS:

  • ✅ are free, fast, reliable
  • ✅ support IPv4 and IPv6
  • ✅ support DNS over TLS4/QUIC5
  • ✅ support DNS over HTTPS67
  • ✅ offer DNS-level malware threat protection
  • ✅ offer child-safety/parental control mode

Only NextDNS:

  • ✅ lets you set your own allow/block domain lists alongside popular Ad-blocking domain lists
  • ✅ lets you turn on/off analytics and/or DNS request logging
    You can enable DNS client-side request logging on Cloudflare WARP application but it’s far from comparable to what proposes NextDNS
  • ✅ lets you customize parental control
  • ✅ lets you create multiple preferences profile
  • ✅ is Web389 ready
    This is not clear for Cloudflare10

I can’t guarantee you I didn’t forget some features but you’ll figure out if you use them.

How to combine both? It seems tricky…

Since I discovered both services, I kept looking for a way to combine them. As you may have noticed, there’s some convenience using Cloudflare WARP as a free VPN and to use NextDNS as a free customizable DNS service. However, using both at the same time is not easily possible.

1st Idea: Use both official client applications

You could install both applications on mobile and/or desktop and try to enable them alongside each other. You’ll figure out that it’s not working as you expected. NextDNS will be enabled but WARP, once active, will bypass NextDNS and redirect all traffic to Cloudflare WARP.

2nd Idea: Use Cloudflare WARP Proxy feature alongside NextDNS official client

I wrote about it on Reddit weeks ago and it’s an interesting solution. Cloudflare has a proxy feature that can be used alongside NextDNS. This feature is designed to redirect traffic from a specific application to the Cloudflare network with the downside that DNS resolution is disabled. But as you can understand, we’re not interested in Cloudflare DNS resolution, so this is not a problem.

Now, the only thing you have to do is to use NextDNS official client application and set WARP as a proxy on OS level. You can also change your Network Settings and manually replace DNS addresses by ones from NextDNS. To ensure that every interface will use WARP Proxy, I made a script (in fish language, sorry) to set the proxy and DNS addresses on every interface on macOS:


# Author: Guillaume Coquard
# This script only accepts "on" or "off" as argument.


PROXY_PORT="____"       # Change this with the port you want to use
PROXY_ADDR=""  # This can also be

# Test if warp-cli is installed
if ! which warp-cli > /dev/null; then
    echo "Cloudflare WARP is not installed or not in your PATH. Please install it first."
    # Test if brew is installed
    if ! which brew > /dev/null; then
        echo "You can install it via brew install --cask cloudflare-warp."
        echo "Homebrew is not installed or not in your PATH. Please install Homebrew first."
        echo "Visit https://brew.sh/."
        exit 1
        echo "You can install it via brew install --cask cloudflare-warp."
        exit 1

sudo "${WAPR_CLI_DIR}/warp-cli" set-mode proxy;
sudo "${WAPR_CLI_DIR}/warp-cli" set-proxy-port "${PROXY_PORT}";

# These IPs are set by NextDNS and specific for each preference profile
NEXTDNSDNS_IPV6=("2a07:a8c0::__:__" "2a07:a8c1::__:__");
NEXTDNSDNS_IPV4=("45.90.__.__" "45.90.__.__");

CLOUDFLAREDNS_IPV6=("2606:4700:4700::1111" "2606:4700:4700::1001");

# Set proxy for every interfaces
for interface in "$(sudo networksetup -listallnetworkservices | grep -v "*")"; do

    # Set proxy for every proxy type
    sudo networksetup -setwebproxy "${interface}" "${PROXY_ADDR}" "${PROXY_PORT}" off;
    sudo networksetup -setsecurewebproxy "${interface}" "${PROXY_ADDR}" "${PROXY_PORT}" off;
    sudo networksetup -setsocksfirewallproxy "${interface}" "${PROXY_ADDR}" "${PROXY_PORT}" off;
    sudo networksetup -setdnsservers "${interface}" ${NEXTDNSDNS_IPV6[@]} ${NEXTDNSDNS_IPV4[@]} ${CLOUDFLAREDNS_IPV6[@]} ${CLOUDFLAREDNS_IPV4[@]};

    # Turn on/off every proxy
    sudo networksetup -setwebproxystate "${interface}" $1;
    sudo networksetup -setsecurewebproxystate "${interface}" $1;
    sudo networksetup -setsocksfirewallproxystate "${interface}" $1;


You can also check the proxy status for every interface with:


# Author: Guillaume Coquard

# Get proxy status for every interfaces
for interface in "$(sudo networksetup -listallnetworkservices | grep -v "*")"; do

    sudo networksetup -getwebproxy "$interface";
    sudo networksetup -getsecurewebproxy "$interface";
    sudo networksetup -getsocksfirewallproxy "$interface";
    sudo networksetup -getdnsservers "$interface"


But there are many potential problems with this solution, starting from the fact that you can’t use other proxies at OS level without third-party software. And also the fact that this is not a reliable solution, requiring one to be confident in relying on Apple Networks Settings that can be buggy from time to time. But if you want to check this yourself, install Wireshark and capture your network.

The 3rd Way: The Good Way

To ensure you’re using both services there’s only one method that guarantees it. Using wgcf tool. This tool has been made by ViRb3, is open-source, and written in Go. The main purpose of wgcf is to generate WireGuard profile from Cloudflare WARP connection.

You just have to:

  1. Register your Cloudflare WARP “environment” with wgcf register ;
  2. Generate a WireGuard profile with wgcf generate --config wgcf-account.toml from the previously registered environment ;
  3. Set the custom DNS IP addresses directly in the generated profile ;
  4. Use the generated profile within the WireGuard client ;
  5. Enable your newly created WireGuard configuration within the WireGuard client.
PrivateKey = [base64-encoded-private-key]
Address =
Address = fd01:5ca1:ab1e:8a29:f19:cf4:a32:298/128
MTU = 1280
PublicKey = [base64-encoded-public-key]
AllowedIPs =
AllowedIPs = ::/0
Endpoint = engage.cloudflareclient.com:2408

This is the file generated in step 2.

For the remaining steps we need to use a WireGuard client and to do so we’ll use the official one for macOS.

WireGuard on the macOS App Store
WireGuard on the macOS App Store
Screenshot of WireGuard application
Import a "Tunnel" from a file
You should obtain something like that

Then you add your custom NextDNS IP addresses as shown below:

PrivateKey = [base64-encoded-private-key]
Address =
Address = fd01:5ca1:ab1e:8a29:f19:cf4:a32:298/128
DNS = 2a07:a8c0::__:__, 2a07:a8c1::__:__
DNS = 45.90.__.__, 45.90.__.__
DNS = 2606:4700:4700::1111, 2606:4700:4700::1001
DNS =,
MTU = 1280
PublicKey = [base64-encoded-public-key]
AllowedIPs =
AllowedIPs = ::/0
Endpoint = engage.cloudflareclient.com:2408

Once everything is set up, you should not see any red-underlined text. I also recommend adding standard listening port in the “Interface” configuration block:

ListenPort = 53

It should prevent anyone who tries to block your VPN to achieve it. Your Internet traffic will be shown as DNS packets on the network.

Eventually, you'll likely get this

Now, you can enable “On-Demand” for Ethernet or WiFi mode to ensure your device connects to this tunnel whatever you’re doing. Click “Save”.

Finally, you’ll get your profile set:

WireGuard with Mixed Profile Saved
WireGuard with Mixed Profile Saved

And now, you just have to enable it:

WireGuard with Mixed Profile Enabled


To illustrate it better, I have set my NextDNS profile to block most of the ads thanks to the NextDNS predefined ad-blocking domain lists. Here are some french press websites, on the left the Home profile is enabled, on the right, it is disabled:

Comparison on liberation.fr: Left: Enabled / Right: Disabled
Comparison on figaro.fr: Left: Enabled / Right: Disabled
Comparison on lemonde.fr: Left: Enabled / Right: Disabled
Comparison of packet traffic from/to current device: Left: Enabled / Right: Disabled


Your traffic is now mostly private and nobody can see what you’re doing on the network. The cool thing is that wgcf tool is cross-platform, as WireGuard client is, so you can use the same WireGuard profile on all your computers but also on your mobile devices.

  1. Introducing WARP: Fixing Mobile Internet Performance and Security, Cloudflare

  2. Introducing DNS Resolver, (not a joke), Cloudflare

  3. BoringTun, a userspace WireGuard implementation in Rust, Cloudflare

  4. DNS over TLS, Wikipedia

  5. QUIC, Wikipedia

  6. DNS over HTTPS, Wikipedia

  7. DNS over TLS vs. DNS over HTTPS, Cloudflare

  8. Web3, Wikipedia

  9. “NextDNS now supports [web3]“, @NextDNS

  10. Web3, Cloudflare