What steps will reproduce the problem?
1. Attempt to resolve authoritative FQDN from a misbehaving NS.
2. Observe a record of type other than 'CNAME' returned.
What is the expected output? What do you see instead?
Incorrect CNAME resolution.
Original issue reported on code.google.com by b...@byrion.com on 3 Feb 2012 at 11:45
Original issue reported on code.google.com by
b...@byrion.com
on 3 Feb 2012 at 11:45