From 3411f7fe60ab7cc7fe022e8af8d7a1aab8061571 Mon Sep 17 00:00:00 2001 From: Joey Hafner Date: Wed, 9 Nov 2022 15:29:28 -0800 Subject: [PATCH] Embed DNS resolve error images --- docs/DNS Resolution.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/DNS Resolution.md b/docs/DNS Resolution.md index bf094f0..3ab4398 100644 --- a/docs/DNS Resolution.md +++ b/docs/DNS Resolution.md @@ -20,8 +20,8 @@ A client can be manually configured to request DNS resolution from the router, w DNS requests to the PiHole will be checked against the [configured adlists](https://pihole.jafner.net/groups-adlists.php). If matched, the request will be blocked. If a user is attempting to access a website that is blocked, the request should quickly resolve to a Domain Not Found error. It will look like this: -[Chrome](/docs/img/pihole_domain_blocked_chrome.png) -[Firefox](/docs/img/pihole_domain_blocked_firefox.png) +![Chrome](/docs/img/pihole_domain_blocked_chrome.png) +![Firefox](/docs/img/pihole_domain_blocked_firefox.png) If the request does not match any adlists, it will be passed upstream to Google `8.8.8.8` (or backup `8.8.4.4`). Presently, the PiHole does not cache any requests.