<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <?xml-stylesheet href="/s/inc/rss.xsl" type="text/xsl"?>
    <rss version="2.0"  xmlns:atom="http://www.w3.org/2005/Atom">
        <channel>
            <title>RSS feed for tag traceroute on Raymii.org</title> 
            <link>https://raymii.org/s/tags/traceroute.xml</link> 
            <description>RSS feed for tag traceroute on Raymii.org</description>
            <atom:link href="https://raymii.org/s/tags/traceroute.xml" rel="self" type="application/rss+xml" />
    
            <item>
                <title>FreeIPA DNS workaround for DNS zone [...]. already exists in DNS and is handled by server(s):</title> 
                <link>https://raymii.org/s/snippets/FreeIPA_DNS_workaround_for_DNS_zone_already_exists_in_DNS_and_is_handled_by_servers.html?utm_medium=rss&amp;utm_source=raymii&amp;utm_campaign=tagrss</link> 
                <guid>https://raymii.org/s/snippets/FreeIPA_DNS_workaround_for_DNS_zone_already_exists_in_DNS_and_is_handled_by_servers.html</guid>
                <description>Recently I ran into an issue with FreeIPA when trying to add an existing DNS zone. The zone already exists on the internet so, logically, FreeIPA wouldn't allow me to hijack this domain locally. My usecase is special, so I wanted to forcefully add this zone as a forward zone.</description> 
                <pubDate>Tue, 10 Apr 2018 00:00:00 GMT</pubDate>
                <lastBuildDate>Tue, 10 Apr 2018 00:00:00 GMT</lastBuildDate>
            </item>
    
            <item>
                <title>Traceroute IPv6 to Smokeping Target config</title> 
                <link>https://raymii.org/s/snippets/IPv6_Traceroute_to_Smokeping_Target_Config.html?utm_medium=rss&amp;utm_source=raymii&amp;utm_campaign=tagrss</link> 
                <guid>https://raymii.org/s/snippets/IPv6_Traceroute_to_Smokeping_Target_Config.html</guid>
                <description>This little one-liner converts the output of traceroute for IPv6 to Smokeping Target output. I had only setup my smokepings for IPv4. Recently we had an issue were network config was borked and the whole IPv4 network was not announced via BGP anymore. I was at home troubleshooting, but finding nothing since I have native IPv6 and that part still worked. My Smokeping did show loss, and that explicitly uses IPv4. That helped with the debugging a lot. I have a [IPv4][4] version of this article as well.</description> 
                <pubDate>Sun, 05 Mar 2017 00:00:00 GMT</pubDate>
                <lastBuildDate>Sun, 05 Mar 2017 00:00:00 GMT</lastBuildDate>
            </item>
    
            <item>
                <title>Traceroute to Smokeping Target config</title> 
                <link>https://raymii.org/s/snippets/Traceroute_to_Smokeping_Target_Config.html?utm_medium=rss&amp;utm_source=raymii&amp;utm_campaign=tagrss</link> 
                <guid>https://raymii.org/s/snippets/Traceroute_to_Smokeping_Target_Config.html</guid>
                <description>This little one-liner converts the output of traceroute to Smokeping Target output. This way you can build your smokeping config faster.</description> 
                <pubDate>Sat, 28 Jun 2014 00:00:00 GMT</pubDate>
                <lastBuildDate>Sat, 28 Jun 2014 00:00:00 GMT</lastBuildDate>
            </item>
    
        </channel>
    </rss>
    
    