On 11Apr23, Warren Kumari apparently wrote: > lame delegation > lame server
Notwithstanding an unresponsive/unreachable server, perhaps due to an ephemeral network error, is there any scenario where a misconfigured server is not described as lame in some way? Put another way, fixing a lame situation *always* requires a configuration change somewhere in the resolution path, yes? Conversely, does it follow that there are no configuration errors which are not lame? Perhaps mild inconsistencies such as SOAs differing or TTLs differing are considered not to be lame. So de-laming always requires adding/subtracting/editing one or more NS/A/AAAA RRs, yes? Mark. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
