<?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-03-31T21:29:00+00:00</dc:date>

	
	<item>
		<title> Open DNS Resolvers - Coming to an IP Address Near You! (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20130402_open_dns_resolvers_coming_to_an_ip_address_near_you</guid>
		<link>https://circleid.com/posts20130402_open_dns_resolvers_coming_to_an_ip_address_near_you</link>
		<description><![CDATA[Three vectors were exploited in the recent DDoS attack against Spamhaus: 1) Amplification of DNS queries through the use of DNSSEC signed data; 2) Spoofed source addresses due to lack of ingress filtering (BCP-38) on originating networks; 3) Utilisation of multiple open DNS resolvers While. 1) is unavoidable simply due to the additional data that DNSSEC produces, and 2) "should" be practised as part of any provider's network configuration, it is 3) that requires "you and I" ensure that systems are adequately configured.  <a href="https://circleid.com/posts20130402_open_dns_resolvers_coming_to_an_ip_address_near_you">More...</a>]]></description>
		<dc:date>2026-03-31T14:29:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>