Hello, I am currently out of the office until January 2nd.
If this is an urgent message please reach out to my manager Robert Kisteleki or myself directly at +31 643419539. Happy holidays :) Guy Meyer On 6 Oct 2022, at 19:11, Karsten Thomann via ripe-atlas <ripe-atlas@ripe.net> wrote: > On Thursday, 6 October 2022 19:42:58 EEST netravnen+ripel...@gmail.com wrote: > On Thu, 6 Oct 2022 at 13:32, Simon Brandt via ripe-atlas > > <ripe-atlas@ripe.net> wrote: > If the distinction isn't to difficult to implement, I would prefer these > three types as system tags: > > Inside-AS DNS > Outside-AS DNS > RFC1918 DNS > > Agreed, these three tags would IMO satisfy *most* use cases. Certainly > mine, too. > I'm now curious how that would work with dual-stack probes using different > providers for v4 and v6... > > My probe uses my local Provider for v4 and HE for IPv6 (static /48 network > with reverse dns delegation would never be possible from my local provider). > According to that logic, using my local router as dns server for the probe, > could set all three tags depending on the used dns server. > As an example depending on the transport protocol used for dns: > - v4 uses RFC1918 IP as resolver IP and inside AS DNS Server > - v6 uses public IP of subnet and resolves via a different AS if the query is > sent over v6 > It could also be argued, that the v6 case is still Inside-AS DNS, but it > should be clear how the tags are determined. > > Or is this case in the meantime special enough to ignore it due to the rising > native v6 rollout by providers? > > > > -- > ripe-atlas mailing list > ripe-atlas@ripe.net > https://lists.ripe.net/mailman/listinfo/ripe-atlas
-- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas
