<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Server Blocks on My IT Journal</title>
    <link>https://my-it-blog.netlify.app/tags/server-blocks/</link>
    <description>Recent content in Server Blocks on My IT Journal</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 04 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://my-it-blog.netlify.app/tags/server-blocks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Configuring Reverse DNS (PTR Records) with BIND9</title>
      <link>https://my-it-blog.netlify.app/posts/reverse-dns/</link>
      <pubDate>Sat, 04 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://my-it-blog.netlify.app/posts/reverse-dns/</guid>
      <description>&lt;h1 id=&#34;configuring-reverse-dns-ptr-records-with-bind9&#34;&gt;Configuring Reverse DNS (PTR Records) with BIND9&lt;/h1&gt;
&lt;h2 id=&#34;objective&#34;&gt;Objective&lt;/h2&gt;
&lt;p&gt;Extend the existing private DNS infrastructure by configuring Reverse DNS (PTR records). This enables IP addresses to be resolved back to hostnames, complementing the forward lookup zone created in previous labs.&lt;/p&gt;
&lt;p&gt;By the end of this lab, the DNS server will support both:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Forward lookups (hostname → IP address)&lt;/li&gt;
&lt;li&gt;Reverse lookups (IP address → hostname)&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&#34;environment&#34;&gt;Environment&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Virtualization: VirtualBox&lt;/li&gt;
&lt;li&gt;OS: ( 1 DNS Server VM + 1 Web Server VM + 1 Client VM)&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&#34;network-topology&#34;&gt;Network Topology&lt;/h2&gt;
&lt;p&gt;&lt;img alt=&#34;dns-topology&#34; loading=&#34;lazy&#34; src=&#34;https://my-it-blog.netlify.app/posts/reverse-dns/dns-topology.png&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hosting Multiple Websites on One Server Using Nginx</title>
      <link>https://my-it-blog.netlify.app/posts/nginx-virtual-hosts/</link>
      <pubDate>Fri, 03 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://my-it-blog.netlify.app/posts/nginx-virtual-hosts/</guid>
      <description>&lt;h1 id=&#34;hosting-multiple-websites-on-one-server-using-nginx&#34;&gt;Hosting Multiple Websites on One Server Using Nginx&lt;/h1&gt;
&lt;h2 id=&#34;objective&#34;&gt;Objective&lt;/h2&gt;
&lt;p&gt;Host multiple websites on a single web server by combining:&lt;/p&gt;
&lt;p&gt;DNS (BIND9)
Nginx Virtual Hosts (Server Blocks)&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;environment&#34;&gt;Environment&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Virtualization: VirtualBox&lt;/li&gt;
&lt;li&gt;OS: ( 1 DNS Server VM + 1 Web Server VM + 1 Client VM)&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&#34;network-topology&#34;&gt;Network Topology&lt;/h2&gt;
&lt;p&gt;&lt;img alt=&#34;dns-topology&#34; loading=&#34;lazy&#34; src=&#34;https://my-it-blog.netlify.app/posts/nginx-virtual-hosts/dns_vhost_topology.png&#34;&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;/h2&gt;
&lt;p&gt;This lab builds upon the Private DNS Infrastructure with BIND9 (3-VM Lab). The following components are assumed to already be configured:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;BIND9 installed and running on the DNS server.&lt;/li&gt;
&lt;li&gt;The company.lab DNS zone created and configured.&lt;/li&gt;
&lt;li&gt;The zone file (/etc/bind/db.company.lab) already exists.&lt;/li&gt;
&lt;li&gt;The client is configured to use the internal DNS server (192.168.10.10) via Netplan.&lt;/li&gt;
&lt;li&gt;DNS resolution between the client and the DNS server has been verified.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In this lab, the existing DNS infrastructure is extended by adding additional DNS records and configuring Nginx virtual hosts to host multiple websites on a single web server.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
