I've also tried to 'compile' nsd zone into unbound syntax. That is: i've done something like that: local-zone: "example.com." transparent local-data: "computer.example.com. IN A 192.168.2.4"
That works as with stub-zone, i.e: if computer.example.com has also AAAA record on upstream server - it will not be fetched. If there is following record on upstream server: computer2.example.com IN CNAME computer.example.com. computer IN A 12.13.14.15 Resolved ip for computer2.example.com will be 12.13.14.15, not 192.168.2.4. And that's strange - as shown by logs, unbound drops ... IN A reply from upstream server when it get CNAME and then running query again for CNAME value, but without checking for local zones. If local zones are done for replacing some records (not all - stub zone will replace full zone) with local - second issue is strange. If local zones are done for adding some local record - first issue is strange. Any ideas about how it may be worked around? -- Andrian Nord _______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
