<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Csharp on GeekyRyan</title><link>https://rnemeth90.github.io/tags/csharp/</link><description>Recent content in Csharp on GeekyRyan</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 17 Aug 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://rnemeth90.github.io/tags/csharp/index.xml" rel="self" type="application/rss+xml"/><item><title>DnsPinger: A Small .NET Tool for Diagnosing DNS Issues in Kubernetes</title><link>https://rnemeth90.github.io/projects/2023-08-17-dnspinger/</link><pubDate>Mon, 17 Aug 2026 09:00:00 +0000</pubDate><guid>https://rnemeth90.github.io/projects/2023-08-17-dnspinger/</guid><description>&lt;p&gt;DNS problems in Kubernetes are some of the most frustrating issues to chase down. They&amp;rsquo;re often intermittent, they can differ by node, by node pool, by which resolver actually answered the query, and the standard toolbox (&lt;code&gt;nslookup&lt;/code&gt;/&lt;code&gt;dig&lt;/code&gt; run once by hand) doesn&amp;rsquo;t tell you much about a problem that only shows up 1% of the time or only on certain nodes. I got tired of manually reproducing DNS flakiness during incidents, so I wrote &lt;strong&gt;DnsPinger&lt;/strong&gt; — a small, purpose-built .NET console application that continuously exercises DNS resolution from inside the cluster and reports what it finds.&lt;/p&gt;</description></item></channel></rss>