This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Tagging probes which are using the ISP's DNS server?
- Previous message (by thread): [atlas] Tagging probes which are using the ISP's DNS server?
- Next message (by thread): [atlas] Tagging probes which are using the ISP's DNS server?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Niall O'Reilly
niall.oreilly at ucd.ie
Tue Oct 11 13:04:46 CEST 2022
On 10 Oct 2022, at 13:42, Robert Kisteleki wrote: > Here's a quick-and-dirty answer to this: what the tags could look like > if we applied them. This is about the ~12K connected probes, which > collectively have ~23K resolver entries. Note: in this experiment the > "more specific tags win", i.e. if quad1 is applied, then outside-asn > tag is not. Thanks for this quick and useful report, Robert. What I take from it is that - (a) for most of the categories of interest, the one which (most closely) matches a given probe may readily be determined, and - (b) only one category seems ambiguous with regard to Max's original question, since "inside ASN" doesn't necessarily correspond to "using the ISP's DNS server". I'm wondering whether this ambiguity matters in the context of Max's question, and reckon that his opinion on this is a significant one. For my own network, I have always the option of reconfiguring to use ULA/RFC1918 (both private) instead of GLA/RFC1918 (inside-ASN/private). Thanks again, Niall (hat off)
- Previous message (by thread): [atlas] Tagging probes which are using the ISP's DNS server?
- Next message (by thread): [atlas] Tagging probes which are using the ISP's DNS server?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]