<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Jul 13, 2015, at 10:34 AM, Lucio Crusca <<a href="mailto:lucio@sulweb.org" class="">lucio@sulweb.org</a>> wrote:<div class="">[ ... ]<br class=""><div><blockquote type="cite" class=""><div class=""><span style="font-family: Monaco; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Yes the zone failed to update, I know because if I raise the seqno @ns1, it tries to update and it keeps failing. I don't understand why it fails. I doubt a Cisco router is to blame here because ns1 and ns2 are two guests of the same host, no routers between them.</span></div></blockquote></div><br class=""><div class="">Note that one should put your nameservers on different physical hardware to ensure high availability.</div></div><div class=""><br class=""></div><div class="">(Different HW located in different datacenters using different upstream network providers, ideally....)</div><div class=""><br class=""></div><div class="">Regards,</div><div class="">-- </div><div class="">-Chuck</div><div class=""><br class=""></div></body></html>