Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jdnssec verify can not handle CAA records #9

Closed
SvenVD-be opened this issue Feb 13, 2019 · 1 comment
Closed

jdnssec verify can not handle CAA records #9

SvenVD-be opened this issue Feb 13, 2019 · 1 comment

Comments

@SvenVD-be
Copy link

SvenVD-be commented Feb 13, 2019

org.xbill.DNS.Tokenizer$TokenizerException: dns.be.zone.forfast.axfr:30: Invalid type 'CAA'
at org.xbill.DNS.Tokenizer.exception(Tokenizer.java:710)
at org.xbill.DNS.Master.parseTTLClassAndType(Master.java:161)
at org.xbill.DNS.Master._nextRecord(Master.java:364)
at org.xbill.DNS.Master.nextRecord(Master.java:388)
at com.verisignlabs.dnssec.security.ZoneUtils.readZoneFile(ZoneUtils.java:74)
at com.verisignlabs.dnssec.cl.VerifyZone.execute(VerifyZone.java:141)
at com.verisignlabs.dnssec.cl.CLBase.run(CLBase.java:336)
at com.verisignlabs.dnssec.cl.VerifyZone.main(VerifyZone.java:164)

version jdnssec-tools-0.14-0

@dblacka
Copy link
Owner

dblacka commented Feb 26, 2019

0.14 had a version of dnsjava.jar without a CAA implementation. This was odd because the version number matched what we had in jdnssec-dnsjava, and that did have an implementation. Updating the jar fixes this issue.

@dblacka dblacka closed this as completed Feb 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants