diff --git a/content/u/blog/the-v6-pattern-for-proxied-hosts/2021-02-24-183437_817x476_scrot.png b/content/u/blog/the-v6-pattern-for-proxied-hosts/2021-02-24-183437_817x476_scrot.png
new file mode 100644
index 0000000..7b8f4c3
Binary files /dev/null and b/content/u/blog/the-v6-pattern-for-proxied-hosts/2021-02-24-183437_817x476_scrot.png differ
diff --git a/content/u/blog/the-v6-pattern-for-proxied-hosts/contents.lr b/content/u/blog/the-v6-pattern-for-proxied-hosts/contents.lr
new file mode 100644
index 0000000..f20d288
--- /dev/null
+++ b/content/u/blog/the-v6-pattern-for-proxied-hosts/contents.lr
@@ -0,0 +1,31 @@
+title: The v6 pattern for IPv6 only hosts
+---
+pub_date: 2021-02-24
+---
+author: ungleich
+---
+twitter_handle: ungleich
+---
+_hidden: no
+---
+_discoverable: yes
+---
+abstract:
+How to configure proxied IPv6 only hosts reliably.
+---
+body:
+
+At ungleich we have a lot of IPv6-only web servers. Many of them are
+are proxied from the IPv4 world, so the domain name points to two
+different machines:
+
+* the AAAA entry points to the server directly
+* the A entry points to a proxy
+
+This  sometimes makes configuring the right system a bit harder,
+because on dual stack clients, accessing www.example.com brings you to
+either machine. In the [first ungleich tech
+talk](https://www.youtube.com/watch?v=cANwo0IdZYU) we show how this
+looks in detail and how we ensure that we configure the right machine.
+
+This is our first tech talk and we love to [hear your feedback](/u/contact/).