I don't understand your scenario. Can you flesh it out a bit? It seems to me that I would expect SERVFAIL in this type of scenario (spoofing is successful, the answer should be signed, but the spoofed answer isn't signed). What happens exactly, there's ISC BIND running somewhere, as a recursive server for the client resolver ? What if anything in your scenario is actually configured as DNSSEC secured and has a good trust anchor? What is it requesting? What does it receive? Or maybe you have a link to a bug report which explains all this? There are extensive test zones available, so you don't need to rely on hypotheticals, every combination people could think of exists (in these test zones, and no doubt soon on the public Internet due to ordinary incompetence). If your scenario requires a CNAME which is unsigned but which points to a signed A record from the same zone, there's a test for that. How about a correctly signed CNAME, plus an A record signed with an expired key and a TXT record which is correctly signed but by a key which is not yet valid (DNSSEC pre-issues keys)? We can do that. Nothing needs to be spoofed, because the test zones contain everything a spoofer might want to send (and plenty of things no-one ever has any reason to send but which might conceivably exist anyway)
Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds