How would you like to setup DR for DNS Servers.

[KapilRaj]

Any ideas ?. I have a slave DNS server at the DR location. I intend to convert that as the primary in the event of a DR. So that I can modify the production client facing application FQDN's to be configured as aliases to their DR counterparts. I have TTL set for 2 days and that is almost close to our DR SLA.

I would appreciate valid suggessions..

Thanks,

Kaps

[Steven E. Protter]

Shalom Kaps,

If this is an independent DR test, as in the system is not connected to or needs to interact with the main office:

You can take the zone records for your FQDN/DNS database straight into the DR center unmodified.

If the connection will be open for hot data copy and such, you can add to the central DNS server entries for the DR servers and set up a caching only DNS server in the DR center.

I hope this is a valid suggestion. I don't know what the acronym SLA stands fore and that made it slightly more difficult to answer this query.

SEP

[Chris Hendrick_2]

SLA - Service Level Agreement...

[Ivan Krastev]

Hi Kapil,

you can try with some scripts to watch/monitor other (master) and restart slave DNS with another configuration file - prepared for this to become master. You already have zone db files.

SEP: Service Level Agreement = SLA

:D

regards,
ivan

[KapilRaj]

Would you recommend to place the Primary DNS in the DR location than the production site?. The advantage is that , I don't have to convert one of the slave to primary incase of a disaster. Also it does not make any diffrence to the Production as long as I keep couple of slave servers in the Production site.

Am I correct in making that statement ?

Regards,

Kaps

[KapilRaj]

Just brought it on top. So experts can see this thread.

[Kevin Wright]

That could work, as long as the you don't have to make emergency changes if the DR site fails.

It sounds like you are concerned you will have to make changes if you prod dns server is not avail? if that is a major concern, I would suggest to keep prod configuration files on one of your slave servers. Then you can restart named on the slave as a primary