<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>System-Administration on Compile My Mind</title>
		<link>https://www.compilemymind.com/categories/system-administration/</link>
		<description>Recent content in System-Administration on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Wed, 15 Jul 2026 20:08:42 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/categories/system-administration/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Windows DNS Diagnostics with PowerShell: A Safe Troubleshooting Workflow</title>
				<link>https://www.compilemymind.com/posts/troubleshooting-windows-dns-powershell/</link>
				<pubDate>Wed, 15 Jul 2026 20:08:42 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/troubleshooting-windows-dns-powershell/</guid>
				<description>&lt;h2 id=&#34;direct-answer&#34;&gt;Direct answer&lt;/h2&gt;&#xA;&lt;p&gt;Windows DNS failures should be separated into three questions: does the machine have the expected interface and resolver settings, can it reach a resolver, and does the resolver return the record being requested? &lt;code&gt;Get-NetIPConfiguration&lt;/code&gt;, &lt;code&gt;Test-NetConnection&lt;/code&gt;, and &lt;code&gt;Resolve-DnsName&lt;/code&gt; answer those questions without changing the adapter or DNS cache. This guide is for administrators who need a safe, repeatable diagnosis before changing DHCP, firewall, or server configuration.&lt;/p&gt;&#xA;&lt;h2 id=&#34;start-with-local-configuration&#34;&gt;Start with local configuration&lt;/h2&gt;&#xA;&lt;p&gt;&lt;code&gt;Get-NetIPConfiguration&lt;/code&gt; shows the interface, address, gateway, and DNS server assignments that Windows is using. Save the output before making a change. A missing address, an unexpected gateway, or a resolver from the wrong network explains many apparent DNS failures.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Common Kubernetes Probe Misconfigurations and Fixes</title>
				<link>https://www.compilemymind.com/posts/kubernetes-probe-misconfigurations-fixes/</link>
				<pubDate>Wed, 15 Jul 2026 19:31:37 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/kubernetes-probe-misconfigurations-fixes/</guid>
				<description>&lt;h2 id=&#34;direct-answer&#34;&gt;Direct answer&lt;/h2&gt;&#xA;&lt;p&gt;Kubernetes probes fail when the check does not match the application&amp;rsquo;s startup time, listening address, endpoint, or expected response. A liveness probe decides whether a container should be restarted, a readiness probe decides whether traffic should be sent, and a startup probe gives a slow-starting container time to initialize before the other checks matter. Diagnose the probe type first, then verify the command, HTTP path, port, and timing values against the running Pod.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Troubleshooting Windows Event Logs with PowerShell</title>
				<link>https://www.compilemymind.com/posts/troubleshooting-windows-event-logs-powershell/</link>
				<pubDate>Wed, 15 Jul 2026 18:49:56 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/troubleshooting-windows-event-logs-powershell/</guid>
				<description>This article guides system administrators on troubleshooting Windows Event Logs using PowerShell&amp;rsquo;s Get-WinEvent and the wevtutil command-line tool, focusing on efficient, read-only queries, filtering, remote access, and safe export techniques.</description>
			</item>
	</channel>
</rss>
