<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;Re: Single Point of Failure&#x27; in forum &#x27;&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21793779</link>
<description></description>
<language>en</language>
<pubDate>Fri, 10 Feb 2012 16:53:13 EDT</pubDate>
<lastBuildDate>Fri, 10 Feb 2012 16:53:13 EDT</lastBuildDate>

<item>
<title>Re: Single Point of Failure</title>
<link>http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21796147</link>
<description><![CDATA[anon posted : Sue them for loss of business so next time they won't screw up. It's not like this has never happened to anyone else out there...]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21796147</guid>
<pubDate>Fri, 23 Jan 2009 20:26:03 EDT</pubDate>
</item>

<item>
<title>Re: Single Point of Failure</title>
<link>http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21794038</link>
<description><![CDATA[Matt posted : <div class="bquote"><small>said by <a href="/profile/906493" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=906493');">knightmb</a>:</small><br><br><div class="bquote"><small>said by <a href="/profile/843138" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=843138');">Matt</a>:</small><br><br>Interesting, I've always thought of the registrars as a pretty critical single point of failure. Does anyone have a creative solution for this?<br> </div>Static IP with DNS backup.<br><br>Basically, the device uses the same static IP and if the login for it doesn't work, check the DNS to refresh the new static IP. Check backup DNS if the first one fails for login. Pretty straight forward really, that's what my Vonage router does, it can work in a DNS outage.<br> </div>That's a good idea, but the problem with it is that the device has to support it. That doesn't translate well to a web infrastructure, or any email where the user has to input the information to reach the site.<br><br>I was thinking of something along the lines of multiple registrars for a single domain ... and if one returned an NXDOMAIN or any other sort of error, DNS would check the secondary registrar. I think my idea would require a significant change to the entire DNS infrastructure though. :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21794038</guid>
<pubDate>Fri, 23 Jan 2009 13:19:08 EDT</pubDate>
</item>

<item>
<title>Re: Single Point of Failure</title>
<link>http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21793973</link>
<description><![CDATA[jester121 posted : For a single domain? There's only one date.<br><br>How about, don't dick around with DNS settings when you're doing a renewal? If there's one thing I've learned about DNS, it's "one thing at at time". If you're doing a transfer, don't switch hosts for a week or so. If you're moving to a new host, don't try to transfer registrars. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21793973</guid>
<pubDate>Fri, 23 Jan 2009 13:08:29 EDT</pubDate>
</item>

<item>
<title>Re: Single Point of Failure</title>
<link>http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21793949</link>
<description><![CDATA[knightmb posted : <div class="bquote"><small>said by <a href="/profile/843138" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=843138');">Matt</a>:</small><br><br>Interesting, I've always thought of the registrars as a pretty critical single point of failure. Does anyone have a creative solution for this?<br> </div>Static IP with DNS backup.<br><br>Basically, the device uses the same static IP and if the login for it doesn't work, check the DNS to refresh the new static IP. Check backup DNS if the first one fails for login. Pretty straight forward really, that's what my Vonage router does, it can work in a DNS outage.<br><small>--<br>Fight NebuAD and the like:<br><A HREF="http://wanip.org/anti-nebuad/">Click Here to pollute their data</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21793949</guid>
<pubDate>Fri, 23 Jan 2009 13:04:18 EDT</pubDate>
</item>

<item>
<title>Re: Single Point of Failure</title>
<link>http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21793852</link>
<description><![CDATA[Matt posted : <div class="bquote"><small>said by <a href="/profile/1269402" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1269402');">battleop</a>:</small><br><br>Not a very good one.  You could have a primary / secondary setup where you might have sipserver.primarydomain.com and sipserver.secondarydomain.net and have your domains registered at two different places.   Your equipment would have to support this and you would have to use DNS servers with different domains with different registrars.<br> </div>That's all I've been able to come up with also. I was thinking more related to web infrastructure, so in my case we'd have to somehow notify our clients to use a different FQDN. Not exactly ideal or really even feasible at all.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21793852</guid>
<pubDate>Fri, 23 Jan 2009 12:44:01 EDT</pubDate>
</item>

<item>
<title>Re: Single Point of Failure</title>
<link>http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21793848</link>
<description><![CDATA[deheza posted : Stagger the renewal dates.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21793848</guid>
<pubDate>Fri, 23 Jan 2009 12:42:38 EDT</pubDate>
</item>

<item>
<title>Re: Single Point of Failure</title>
<link>http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21793839</link>
<description><![CDATA[battleop posted : Not a very good one.  You could have a primary / secondary setup where you might have sipserver.primarydomain.com and sipserver.secondarydomain.net and have your domains registered at two different places.   Your equipment would have to support this and you would have to use DNS servers with different domains with different registrars.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Single-Point-of-Failure-21793839</guid>
<pubDate>Fri, 23 Jan 2009 12:41:18 EDT</pubDate>
</item>

<item>
<title>Single Point of Failure</title>
<link>http://www.dslreports.com/forum/Single-Point-of-Failure-21793779</link>
<description><![CDATA[Matt posted : Interesting, I've always thought of the registrars as a pretty critical single point of failure. Does anyone have a creative solution for this?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Single-Point-of-Failure-21793779</guid>
<pubDate>Fri, 23 Jan 2009 12:31:49 EDT</pubDate>
</item>

</channel>
</rss>

