简体   繁体   English

使用DNSimple和CloudFlare的DNS冗余

[英]DNS redundancy with DNSimple and CloudFlare

I have my domain name on DNSimple, my application on Heroku and my name servers on both DNSimple and CloudFlare. 我的域名在DNSimple上,我的应用程序在Heroku上,我的名称服务器在DNSimple和CloudFlare上。

I set up DNSimple so that the first two name servers point to CloudFlare, and the second two point to DNSimple, but often I find that the name servers in DNSimple's UI are reset to all 4 DNSimple name servers. 我设置了DNSimple,以便前两个名称服务器指向CloudFlare,后两个名称服务器指向DNSimple,但是我经常发现DNSimple用户界面中的名称服务器被重置为所有4个DNSimple名称服务器。

Also, when I use whatsmydns to track my domain, I see something strange - some servers have the split DNS configuration, some servers have only DNSimple and others have only CloudFlare. 另外,当我使用whatsmydns跟踪我的域时,我看到了一些奇怪的事情-有些服务器具有拆分的DNS配置,有些服务器只有DNSimple,而另一些只有CloudFlare。 It's been like this for several weeks, so it's not a propogation issue. 像这样已经好几个星期了,所以这不是传播问题。

Any suggestions on how to set this up differently, so that all DNS servers show 2 CloudFlare DNS servers and 2 DNSimple DNS servers? 关于如何进行不同设置的任何建议,以便所有DNS服务器都显示2个CloudFlare DNS服务器和2个DNSimple DNS服务器?

The main goal for this is to be redundant, incase of a DNS failure, like the one DNSimple suffered a while ago. 这样做的主要目的是在DNS发生故障的情况下提供冗余,例如前一个DNSimple遭受的故障。

Rendundancy should not be achieved manually splitting the name servers. 不应通过手动拆分名称服务器来实现冗余。 This approach has a lot of drawbacks. 这种方法有很多缺点。

Just to name a few, DNSimple exposes some custom records. 仅举几例,DNSimple公开了一些自定义记录。 If you use one of those custom records, they will not work on the other provider. 如果您使用这些自定义记录之一,则它们将无法在其他提供程序上使用。

Moreover, you will need to manually keep in sync both providers, which may very likely result in some hard-to-debug issues in case you forget to sync a record, or in the sync you type the wrong value. 此外,您将需要手动使两个提供程序保持同步,这很可能会导致一些难以调试的问题,以防万一您忘记同步记录或在同步中键入错误的值。

Last but not least, in theory, each provider should also be capable to advertise the name servers of the other provider. 最后但并非最不重要的一点是,从理论上讲,每个提供者还应该能够广告另一个提供者的名称服务器。

If you truly want to be redundant, you should use a real secondary DNS system. 如果您确实想要冗余,则应使用真正的辅助DNS系统。 We (DNSimple) will roll this feature out in the next weeks. 我们(DNSimple)将在接下来的几周内推出此功能。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM