 MattAll noise, no signal.Premium
join:2003-07-20
Jamestown, NC
kudos:12 | Single Point of Failure Interesting, I've always thought of the registrars as a pretty critical single point of failure. Does anyone have a creative solution for this? |
|
| 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. |
|
 deheza
join:2004-06-10
Allen, TX | reply to Matt
Stagger the renewal dates. |
|
MattAll noise, no signal.Premium
join:2003-07-20
Jamestown, NC
kudos:12 | reply to battleop
said by battleop: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. 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. |
|
 knightmbEverybody Lies
join:2003-12-01
Franklin, TN | reply to Matt
said by Matt:Interesting, I've always thought of the registrars as a pretty critical single point of failure. Does anyone have a creative solution for this? Static IP with DNS backup.
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.
--
Fight NebuAD and the like:
Click Here to pollute their data |
|
 jester121Premium
join:2003-08-09
Lake Zurich, IL
 ·voip.ms
| reply to deheza
For a single domain? There's only one date.
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. |
|
|
|
MattAll noise, no signal.Premium
join:2003-07-20
Jamestown, NC
kudos:12 | reply to knightmb
said by knightmb:said by Matt:Interesting, I've always thought of the registrars as a pretty critical single point of failure. Does anyone have a creative solution for this? Static IP with DNS backup. 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. 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.
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.  |
|
| reply to Matt
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... |
|
