Resolving and caching illegal names
Marco
mo01 at posteo.de
Wed Jan 25 07:02:40 UTC 2023
Am 24.01.2023 um 12:15:58 Uhr schrieb John Thurston:
> This comes up because my "resolvers" don't actually resolve. All they
> are allowed to do is forward external queries to Akamai, and accept
> the response from Akamai. And Akamai (thank you very much), is happy
> to accept queries like "What is the A-record for 10.11.12.13?" and
> reply with "The answer is 10.11.12.13, and is good for 10 seconds."
>
> Akamai's explanation for this behavior is, ..." the query was made in
> error (likely/maybe meant to be type "PTR") and we are trying to save
> the resolver from doing the work a query like this would entail."
Then Akamai is doing nasty things. Why don't they answer the correct
answer
. 3600 IN SOA a.root-servers.net.
nstld.verisign-grs.com. 2023012500 1800 900 604800 86400
and let applications fail that don't query PTR records in
in-addr.apra/ip6.arpa?
More information about the bind-users
mailing list