I had a similar problem with 'dnscache' from the TinyDNS suite of tools a couple years back. Certain DNS names hosted in AWS Route53 would exceed the max number of requests to be resolved at random, because Route53 randomized the NS records it gave for each subdomain, so every once in awhile during the dns 'walk' dnscache would have to resolve their .net, .co.uk, .org, and .com NS records, which blows up the number of resolutions pretty quickly. Akamai has the same problem. The internet was much simpler 20 years ago :\.
David On Sat, Apr 1, 2017 at 10:04 AM Steve Simon <st...@quintile.net> wrote: > possibly. > > however it didn't take the plan9 community long to figure out what needed > to be changed. Thus, by definition, it was not too obscure. > > -Steve > > > On 1 Apr 2017, at 10:46, Alexandru Gheorghe <alghe.glo...@gmail.com> > wrote: > > > > That's a weird name for CNAME traversing. Should've been (maybe more > > appropriately): "MaxCnameDepth". > > > > > >> On 04/01/2017 04:40 AM, Skip Tavakkolian wrote: > >> Maxretries to > 5 > > > > -- > > ; Alexandru Gheorghe > > ; > > ; <alghe.global gmail com> > > > > >
