Your language and line of questioning leads me to assume that you're perhaps not that familiar with Erlang. Erlang has facilities for running native code within the VM (NIFs and linked-in drivers) and for interacting…
Please post the address of one of these rogue DNS servers.
I let it cache a record, disabled the zone the record came from and left it to expire. It did. I won't deny that it could behave differently from different addresses, but based on the evidence available I'm sure you can…
I just queried ns1.dns.rcn.net for an rrset that has a TTL of 120 seconds and it returned appropriate TTLs. EDIT: It also does the right thing with even shorter TTLs - try `dig 40.2.+.rp.secret-wg.org txt…
Please provide further detail on these '"big" recursive resolvers' that ignore TTLs. I'm yet to see one in the wild and so I'm somewhat dubious of the claim. (Please don't be vague - post the addresses of the resolvers…
Your language and line of questioning leads me to assume that you're perhaps not that familiar with Erlang. Erlang has facilities for running native code within the VM (NIFs and linked-in drivers) and for interacting…
Please post the address of one of these rogue DNS servers.
I let it cache a record, disabled the zone the record came from and left it to expire. It did. I won't deny that it could behave differently from different addresses, but based on the evidence available I'm sure you can…
I just queried ns1.dns.rcn.net for an rrset that has a TTL of 120 seconds and it returned appropriate TTLs. EDIT: It also does the right thing with even shorter TTLs - try `dig 40.2.+.rp.secret-wg.org txt…
Please provide further detail on these '"big" recursive resolvers' that ignore TTLs. I'm yet to see one in the wild and so I'm somewhat dubious of the claim. (Please don't be vague - post the addresses of the resolvers…