<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dns on vnykmshr</title><link>https://blog.vnykmshr.com/writing/tags/dns/</link><description>Recent content in Dns on vnykmshr</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 16 Oct 2012 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.vnykmshr.com/writing/tags/dns/index.xml" rel="self" type="application/rss+xml"/><item><title>The host came back, nginx didn't</title><link>https://blog.vnykmshr.com/writing/the-host-came-back/</link><pubDate>Tue, 16 Oct 2012 00:00:00 +0000</pubDate><guid>https://blog.vnykmshr.com/writing/the-host-came-back/</guid><description>&lt;p&gt;Some paths on the site don&amp;rsquo;t belong to this app. They go to another host &amp;ndash; a second backend behind the same domain &amp;ndash; and nginx forwards them with a &lt;code&gt;proxy_pass&lt;/code&gt;, POST and headers and all. It works, and for months I don&amp;rsquo;t think about it.&lt;/p&gt;
&lt;p&gt;Then the other host goes down for a few minutes. The requests to it fail while it&amp;rsquo;s down &amp;ndash; there&amp;rsquo;s nothing to forward to. That part I expect.&lt;/p&gt;</description></item></channel></rss>