<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="">I found the following article pretty handy in terms of checking a locations connectivity:<div class=""><a href="https://labs.ripe.net/Members/stephane_bortzmeyer/checking-your-internet-connectivity-with-ripe-atlas-anchors" class="">https://labs.ripe.net/Members/stephane_bortzmeyer/checking-your-internet-connectivity-with-ripe-atlas-anchors</a></div><div class="">I've implemented it with great success. These hosts are explicitly on the internet *to* answer ICMP.</div><div class=""><br class=""></div><div class=""><div class="">Theodore Baschak - AS395089 - Hextet Systems<br class=""></div></div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Jun 7, 2016, at 1:16 PM, Andrew White <<a href="mailto:andrew@vivalibre.com" class="">andrew@vivalibre.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi DRC,<div class=""><br class=""></div><div class="">Thanks for your reply. If we have a root server on-net, then I still have the issue of not knowing whether my recursive server has working outbound connectivity; a local copy of the root then moves the issue to the TLD servers.</div><div class=""><br class=""></div><div class="">Andrew</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Jun 7, 2016 at 12:32 PM, David Conrad <span dir="ltr" class=""><<a href="mailto:drc@virtualized.org" target="_blank" class="">drc@virtualized.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br class="">
<span class=""><br class="">
On Jun 7, 2016, at 8:12 AM, Andrew White <<a href="mailto:andrew@vivalibre.com" class="">andrew@vivalibre.com</a>> wrote:<br class="">
> We are considering adding some health checks on our recursive DNS platform.<br class="">
><br class="">
> We'd like to ensure each server has access to the root via a remote dig at the recursive server. Specifically we are considering a query to an effectively random top-level domain that should always be answered by an NXDOMAIN by a root server.<br class="">
><br class="">
> Given the large number of servers and our need to perform this check fairly often, this could result in a large number of queries resulting in NXDOMAIN to the root.<br class="">
<br class="">
</span>Not that it's likely your probes will go above the noise in the noise, why not mirror the root (a la <a href="https://tools.ietf.org/rfc/rfc7706.txt" rel="noreferrer" target="_blank" class="">https://tools.ietf.org/rfc/rfc7706.txt</a>)?<br class="">
<br class="">
Regards,<br class="">
-drc<br class="">
(speaking only for myself)<br class="">
<br class="">
</blockquote></div><br class=""></div>
_______________________________________________<br class="">dns-operations mailing list<br class=""><a href="mailto:dns-operations@lists.dns-oarc.net" class="">dns-operations@lists.dns-oarc.net</a><br class="">https://lists.dns-oarc.net/mailman/listinfo/dns-operations<br class="">dns-jobs mailing list<br class="">https://lists.dns-oarc.net/mailman/listinfo/dns-jobs</div></blockquote></div><br class=""></body></html>