<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>wireguard on Alekc's Blog</title><link>https://blog.alekc.org/tags/wireguard/</link><description>Recent content in wireguard on Alekc's Blog</description><generator>Hugo -- gohugo.io</generator><copyright>©{year}, All Rights Reserved</copyright><lastBuildDate>Sat, 29 Jan 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.alekc.org/tags/wireguard/index.xml" rel="self" type="application/rss+xml"/><item><title>How to expose service behind nat with wireguard and vps</title><link>https://blog.alekc.org/posts/how-to-expose-service-behind-nat-with-wireguard-and-vps/</link><pubDate>Sat, 29 Jan 2022 00:00:00 +0000</pubDate><guid>https://blog.alekc.org/posts/how-to-expose-service-behind-nat-with-wireguard-and-vps/</guid><description>Scenario: you have one (or more) services running at your home which you would like to expose on the internet. Sadly, you are also behind a dynamic dns and your ip can change in any moment.
Sure, you can use one of public dynamic dns providers such as no-ip or zoneedit, but what if you don&amp;rsquo;t want to depend on dns caching from your client and would like to reduce any downtime as much as possible?</description></item></channel></rss>