<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:admin="http://webns.net/mvcb/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:content="http://purl.org/rss/1.0/modules/content/">

	<channel>

	<title>&#45; CircleID</title>
	<link>https://www.circleid.com/blogs/</link>
	<description>Postings from  on CircleID</description>
	<dc:language>en</dc:language>
	<dc:rights>Copyright 2026, unless where otherwise noted.</dc:rights>
	<dc:date>2026-04-06T20:04:00+00:00</dc:date>

	
	<item>
		<title> DNS, My God It's Full of Stars... (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/postsdns_my_god_its_full_of_stars</guid>
		<link>https://circleid.com/postsdns_my_god_its_full_of_stars</link>
		<description><![CDATA[Since my <a href="http://www.circleid.com/posts/just_say_no_isp_subverting_dns_queries/">last post</a> about DNS subversion we have had some good feedback. We had 29 responses, I agree a small sample, but what we found is very interesting. Let's remind ourselves of what we are looking at? Does your ISP redirect DNS queries? Specifically, if you try to make a port 53 UDP or TCP connection to a server outside of your ISP's network does it get there? <a href="https://circleid.com/postsdns_my_god_its_full_of_stars">More...</a>]]></description>
		<dc:date>2026-04-06T13:04:00-07:00</dc:date>
	</item>
	
	<item>
		<title> Just Say No, to Your ISP Subverting Your DNS Queries (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/postsjust_say_no_isp_subverting_dns_queries</guid>
		<link>https://circleid.com/postsjust_say_no_isp_subverting_dns_queries</link>
		<description><![CDATA[Over the past few weeks I have been seeing reports that some ISP's are actually subverting DNS queries to their own DNS server. Oh the humanity! What this means is that when you (your computer) does a UDP or TCP Port 53 DNS query the ISP is intercepting that and directing it to their own servers. Has anyone been told by their ISP that they are doing this? No? I didn't think so... <a href="https://circleid.com/postsjust_say_no_isp_subverting_dns_queries">More...</a>]]></description>
		<dc:date>2026-04-06T13:04:00-07:00</dc:date>
	</item>
	
	<item>
		<title> Dusty Name System (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/postsdusty_name_system</guid>
		<link>https://circleid.com/postsdusty_name_system</link>
		<description><![CDATA[Every IT person has some interaction with a DNS server, even if it is not managing it. Most DNS servers, certainly the majority are sitting in some closet or rack somewhere dutifully running and collecting dust. Like a certain battery operated bunny, these services just keep on running. The durability of DNS (Domain Name System, that is) is a testimony of just how well it was designed... How often do you think about your DNS server? Here is my plan for how to keep your relationship with your DNS server alive and well. <a href="https://circleid.com/postsdusty_name_system">More...</a>]]></description>
		<dc:date>2026-04-06T13:04:00-07:00</dc:date>
	</item>
	
	<item>
		<title> Why DNS Is Broken, Part 2: DoS Target (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20090521_why_dns_is_broken_part_2_dos</guid>
		<link>https://circleid.com/posts20090521_why_dns_is_broken_part_2_dos</link>
		<description><![CDATA[Before we get into what DNSSEC is and the benefits of it, let's talk about some of the other potential pitfalls of DNS. One of the most significant issues we have to deal with are denial-of-service (DoS) attacks. While DoS attacks are not specific to DNS we have seen DNS be a frequent target of these attacks. <a href="https://circleid.com/posts20090521_why_dns_is_broken_part_2_dos">More...</a>]]></description>
		<dc:date>2026-04-06T13:04:00-07:00</dc:date>
	</item>
	
	<item>
		<title> Why DNS Is Broken, Part 1: Trust (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20090408_why_dns_is_broken_part_1_trust</guid>
		<link>https://circleid.com/posts20090408_why_dns_is_broken_part_1_trust</link>
		<description><![CDATA[So this Internet thing, as we discussed in our <a href="http://www.circleid.com/posts/20090323_dns_insecurity/">last article</a>, is broken. I promised to detail some of the specific things that are broken. Implicit trust is the Achilles heel of the Internet... All of the communication between the resolver and the DNS server is in plain text that can be easily seen and changed while in transit, further, the resolver completely trusts the answer that was returned... <a href="https://circleid.com/posts20090408_why_dns_is_broken_part_1_trust">More...</a>]]></description>
		<dc:date>2026-04-06T13:04:00-07:00</dc:date>
	</item>
	
	<item>
		<title> DNS Insecurity (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20090323_dns_insecurity</guid>
		<link>https://circleid.com/posts20090323_dns_insecurity</link>
		<description><![CDATA[The Internet as we know it and use it today -- is broken, badly broken. Yes broken so much so that we are really crazy to have any expectations of privacy or security. Yes, really. The Internet was conceived as somewhat of a utopian environment, one where we all keep our doors, windows and cars unlocked and we trust all the people and machines out there to "do the right thing...". <a href="https://circleid.com/posts20090323_dns_insecurity">More...</a>]]></description>
		<dc:date>2026-04-06T13:04:00-07:00</dc:date>
	</item>
	
	<item>
		<title> This Is Not Your Father's Traceroute Tool (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/poststhis_is_not_your_fathers_traceroute_tool</guid>
		<link>https://circleid.com/poststhis_is_not_your_fathers_traceroute_tool</link>
		<description><![CDATA[Traceroute is a network tool that helps determine the path packets take as they travel from one location to another, identifying all of the "hops" along the way. I wonder why they are called hops*? Almost all operating systems have traceroute utilities built in. The command is just that "traceroute", Windows systems abbreviate the command as "tracert" to deal with the 8.3 file naming convention of old... So, let's look at what information traceroute gives you. <a href="https://circleid.com/poststhis_is_not_your_fathers_traceroute_tool">More...</a>]]></description>
		<dc:date>2026-04-06T13:04:00-07:00</dc:date>
	</item>
	
	<item>
		<title> DNSSEC Rally (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/postsdnssec_rally</guid>
		<link>https://circleid.com/postsdnssec_rally</link>
		<description><![CDATA[In late August the White House mandated that all of the agencies in the US government have functioning DNSSEC capabilities deployed and operational by December 2009. I am suggesting here that we, as a community, commit to the same timetable. I call upon VeriSign and other registries to bring up DNSSEC support by January 2009. <a href="https://circleid.com/postsdnssec_rally">More...</a>]]></description>
		<dc:date>2026-04-06T13:04:00-07:00</dc:date>
	</item>
	
	<item>
		<title> Trust, but Verify (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/poststrust_but_verify</guid>
		<link>https://circleid.com/poststrust_but_verify</link>
		<description><![CDATA[We are at an inflection point in our lifetimes. The Internet is broken, seriously broken... Almost all of the systems currently in use on the Internet are based on implicit trust. This has to change. The problem is that these systems are so embedded in our everyday lives that it would be, sort of like, changing gravity, very difficult. <a href="https://circleid.com/poststrust_but_verify">More...</a>]]></description>
		<dc:date>2026-04-06T13:04:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>