I hadn't had enough coffee when I wrote that. I was doing in-addr.arpa
translation in my head and confusing what was the TLD of the query being
submitted. If a customer is stupid enough to ask for an A-record for
10.1.2.3, then the TLD of that name is "3", not "10" . . duh.
So to make the RPZ
- Why *must* you forward everything to Akamai?
I am forced to "forward only;" to Akamai for all external queries. It
hasn't always been this way, but the decision was made "above my pay
grade", and it is not open to negotiation.
- Was that a real example of a daft query: 10.11.12.13 type
Hi John.
A few questions, if I may.
- Why *must* you forward everything to Akamai?
- Was that a real example of a daft query: 10.11.12.13 type A? If not, do
you have some real examples of queries being made to your servers please?
- Notwithstanding the nature of these illegal queries, if they
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
My "resolvers" running BIND 9.18.10 and 9.16.36, accept and attempt to
resolve queries for illegal names. They will cache answers for these
names, and answer from cache when asked. What's the thinking here?
I suppose it could be, "The specifications of what is a legal name may
change with
5 matches
Mail list logo
