<?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>Dhcp on Technical Notes</title><link>http://luispa.com/en/tags/dhcp/</link><description>Recent content in Dhcp on Technical Notes</description><generator>Hugo -- 0.148.0</generator><language>en-US</language><lastBuildDate>Sun, 09 Mar 2025 00:00:00 +0000</lastBuildDate><atom:link href="http://luispa.com/en/tags/dhcp/index.xml" rel="self" type="application/rss+xml"/><item><title>Home mDNS</title><link>http://luispa.com/en/posts/2025-03-09-mdns/</link><pubDate>Sun, 09 Mar 2025 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2025-03-09-mdns/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-mdns.svg" alt="mDNS Logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>Multicast DNS (mDNS) is a networking protocol designed to resolve hostnames to IP addresses within small networks, without the need for a local DNS server. It requires no configuration (zero-configuration) and uses the same programming interfaces, packet formats and operational semantics as unicast Domain Name System (DNS).&lt;/p>
&lt;p>It was designed to work as either a standalone protocol or alongside standard DNS servers. mDNS can work together with DNS Service Discovery (DNS-SD), a complementary zero-configuration networking technique specified separately in RFC 6763.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Router with PiHole 6</title><link>http://luispa.com/en/posts/2025-03-08-router-pihole/</link><pubDate>Sat, 08 Mar 2025 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2025-03-08-router-pihole/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-piholednsmasq.svg" alt="Pihole Router Logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>A couple of months ago I moved the DHCP and DNS services to my home Linux router and left the Pi-Hole 5 service on a separate virtual machine. Despite everything working perfectly, I hit a snag: troubleshooting from PiHole is complicated because all DNS queries are resolved by the router and PiHole sees nothing. So I decided to redesign the setup.&lt;/p>
&lt;p>In this post I describe how I install Pi-Hole 6 on my Linux router so it provides DNS, DHCP (with dnsmasq) and ad sinkholing. This involves undoing the native dnsmasq installation.&lt;/p>
&lt;br clear="left"/></description></item><item><title>DHCP and DNS Server</title><link>http://luispa.com/en/posts/2024-12-26-dnsmasq/</link><pubDate>Thu, 26 Dec 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-12-26-dnsmasq/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-dnsmasq.svg" alt="dnsmasq logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>In this post I describe how I&amp;rsquo;ve evolved my home DHCP and DNS server. Until now I had a &lt;a href="http://luispa.com/en/posts/2021-06-20-pihole-casero/">PiHole&lt;/a> dedicated on the network to DHCP, DNS and ad sinkhole. I&amp;rsquo;ve decided to migrate to a different configuration, &lt;strong>move both DNS and DHCP services to the home router&lt;/strong> (Linux).&lt;/p>
&lt;p>I realized that when PiHole went down, the rest of the home services would spiral out of control, despite having the router and internet working, so I&amp;rsquo;m leaving PiHole exclusively as the ad sinkhole.&lt;/p>
&lt;br clear="left"/></description></item></channel></rss>