|
Folks: We have our two primary DNS servers on our PepLink 210 WAN Load balancer/Router. We would like to find a way to make those two DNS name servers the ones that are connected to first and if those go down, then and only then we would like DNS lookups to come to a third/forth Name server. This is in case the power goes down in our building for an extended amount of time. You have to understand the point of a Failover WAN Router to fully understand our needs. We simply cannot allow any other DNS server to be used unless our in house DNS name servers hit the floor. We have External Websites and virtual servers that we would not want to lose the ability to have folks reach in the event of a disaster in our building. Is there a way to do that with one of your products as a backup DNS Name Server? If so, is there a way to do a zone transfer into the new DNS name servers so we don't have to start from scratch....? Please advise.... Dale Allen dale@prsoft.com http://www.daleallen.com (787) 637-9100 |
|
Note that this is a user to user forum. The Secondary DNS service means that DynDNS's name servers are updated by your primary DNS server just as your own secondary is - using zone transfers automatically. That means that all name servers will always be in sync - it is no more than an extension of your own secondary DNS server. Note that you have no way of controlling what DNS server a client will chose. That isn't a limitation of DynDNS's service, but the way that DNS works. |
|
About the only way you're going to be able to achieve this is to have your own independent nameserver somewhere, not NECESSARILY listed in the zone's NS RRs, which is already a secondary for the zones in question. On this nameserver you can alter the NS records NOT to point to your in-house servers, then log into Dyn and change the master IP address. (NOTE, YOU DYN PEOPLE, THIS IS NOT "AN IP," WHICH YOU SEEM TO INSIST ON CALLING IT A LOT OF PLACES THROUGHOUT YOUR SITE. IPs are version 4 and version 6 at the moment. The word "address" CAN be important.) When Dyn goes and fetches this new zone data from the new address, it will no longer have your in-house NS listed. You'll also likely have to log into your domain registrar and update the nameserver entries so that the public chooses Dyn and not you. This is to my knowledge the only way to prevent clients from choosing anything other than your nameservers when you're up, and someone else while you're down. Otherwise, as the other poster noted, you have no control over which NS (or other) records which are chosen. The problem is that once the listed DNS servers are down, how do you update the zone to show the new NS records? It can also take between one and 3 days for changes in the domain registration to propagate fully.
May 10 at 04:33 PM
Cry Havok ♦
Aye, there's the rub. That's why I mention you already have to have an independent secondary set up somewhere, which sort of defeats the purpose of Dyn helping out with secondary service. It's the only control we users have: pointing at another IP address. Ideally what this guy'd like is a way to log into Dyn and edit the data once his/er servers go plop, like Custom DNS. It SHOULD work, it's a bit clunky, and as you mentioned the TTL at the root level can be long.
May 10 at 04:41 PM
RChandra
oh, I forgot to mention: you'd have to log into this independent host and update the NS records and remove the in-house ones and replace them with the Dyn ones. for an example with BIND: rndc stop vi /var/named/domainname.zone (make NS record updates, update the SOA serial) /etc/init.d/named start (or whatever is appropriate for your system). The "rndc stop" is critical, as your BIND needs to write out any updates from the .jnl file. Editing them without doing that will probably cause your zone not to load because it will detect there is a discrepancy between the zone file and .jnl
May 10 at 04:46 PM
RChandra
|
