From 0fc1ea12388d4ba1c19555b199ad68dd295be44d Mon Sep 17 00:00:00 2001
From: Blackconvoy88 <39281106+Blackconvoy88@users.noreply.github.com>
Date: Mon, 14 May 2018 16:17:58 -0700
Subject: [PATCH] Spoke with a developr on the PiHole Discourse while trying to
 get this setup working.

---
 DNSCrypt-2.0.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/DNSCrypt-2.0.md b/DNSCrypt-2.0.md
index c07a153..eb852f8 100644
--- a/DNSCrypt-2.0.md
+++ b/DNSCrypt-2.0.md
@@ -27,7 +27,7 @@ There are instructions on the [wiki](https://github.com/jedisct1/dnscrypt-proxy/
 Also see the [wiki](https://github.com/jedisct1/dnscrypt-proxy/wiki/DNS-server-sources) for details on DNS server sources.
 
 ## Step 2: Modify Pi-Hole
-If you're running a newer version of Pi-Hole (might only be available on FTLDNS at the moment), you have the possibility to specify a "**Local DNS server on custom port**" in the Web interface by going to **Settings -> DNS**. Simply check the checkbox and enter 5353 as the port. Of course, you should remove (uncheck) every other DNS server.
+If you're running a newer version of Pi-Hole (might only be available on FTLDNS at the moment), you have the possibility to specify a "**Local DNS server on custom port**" in the Web interface by going to **Settings -> DNS**. Simply check the checkbox and enter 5353 as the port. In newer versions of FTLDNS, this option is no longer present, but all custom DNS fields can now take on a port number with the syntax (**host#port**). Of course, you should remove (uncheck) every other DNS server.
 
 If you're running a older version of Pi-Hole, then follow these instructions:
 * `sudo nano /etc/dnsmasq.d/02-dnscrypt.conf`: Create new or edit existing conf.