diff --git a/content/en/posts/dns-challenge.md b/content/en/posts/dns-challenge.md
index d5a9c85..25e1243 100644
--- a/content/en/posts/dns-challenge.md
+++ b/content/en/posts/dns-challenge.md
@@ -1,6 +1,7 @@
 ---
 title: "How to do HTTPS at home (when your infrastructure is private)"
 date: 2024-09-08T15:18:00+02:00
+lastmod: 2024-09-08T17:20:00+02:00
 draft: false
 toc: true
 images:
@@ -637,7 +638,6 @@ internal.example.com IN SOA ns.internal.example.com. admin.example.com. (
 
 $ORIGIN internal.example.com.
 ns      A     1.2.3.4
-test    A     192.168.1.2
 ```
 
 ### Testing the configuration
@@ -683,3 +683,7 @@ an infrastructure.
 I would argue that a setup of this type is very adapted to homelabs or small businesses
 that have a private infrastructure, but don't want to go through the trouble of setuping
 an entire PKI (Private Key Infrastructure).
+
+## Edits
+
+- 2024-09-08: Fixed [public DNS configuration](#public-dns-server)
diff --git a/content/fr/posts/dns-challenge.md b/content/fr/posts/dns-challenge.md
index f56570c..414d2fa 100644
--- a/content/fr/posts/dns-challenge.md
+++ b/content/fr/posts/dns-challenge.md
@@ -1,6 +1,7 @@
 ---
 title: "Comment faire du HTTPS chez soi (quand son infrastructure est privée)"
 date: 2024-09-08T15:18:00+02:00
+lastmod: 2024-09-08T17:20:00+02:00
 draft: false
 toc: true
 images:
@@ -664,7 +665,6 @@ internal.example.com IN SOA ns.internal.example.com. admin.example.com. (
 
 $ORIGIN internal.example.com.
 ns      A     1.2.3.4
-test    A     192.168.1.2
 ```
 
 ### Tester la configuration
@@ -711,3 +711,7 @@ notre infrastructure.
 Je considère que ce type de setup est particulièrement adapté à un homelab, ou a un business
 de petite taille possédant une infrastructure privée, mais ne souhaitant pas s'infliger
 la création d'une infrastructure PKI (Infrastructure de Clé Privée) complète.
+
+## Corrections
+
+- 2024-09-08: Correction de la [configuration DNS publique](#serveur-dns-public)