From a30dd91218ca123bf0716417b2ea315ab6374c25 Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Wed, 13 Oct 2021 22:47:49 +0900 Subject: [PATCH] Rename ipv6 vpn entry --- .../contents.lr | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) rename content/u/blog/{ipv6-success-story-vpn-dns-names => ipv6-vpn-dns-entries}/contents.lr (97%) diff --git a/content/u/blog/ipv6-success-story-vpn-dns-names/contents.lr b/content/u/blog/ipv6-vpn-dns-entries/contents.lr similarity index 97% rename from content/u/blog/ipv6-success-story-vpn-dns-names/contents.lr rename to content/u/blog/ipv6-vpn-dns-entries/contents.lr index 1fced1f..7ef5ae6 100644 --- a/content/u/blog/ipv6-success-story-vpn-dns-names/contents.lr +++ b/content/u/blog/ipv6-vpn-dns-entries/contents.lr @@ -195,4 +195,6 @@ networks for DNS servers of the destination party. The target party always needs to ensure proper access control to internal resources, so there is no additional overhead. -DNS, correctly designed in the IPv6 VPN world, just works. +DNS, correctly used in the IPv6 VPN world, is a really smooth +operation. This is why we recommend to use +[IPv6 as a basis for VPNs](https://ipv6vpn.ch).