The zone is loaded without any issues with pdnsutil load-zone, but attempt to retrieve zone content using API (/api/v1/servers/localhost/zones/t.z), or attempt to AXFR, or simple query for this RR produces errors:
HTTP ISE for "/api/v1/servers/localhost/zones/example.z": STL Exception: All data was not consumed
TCP Connection Thread died because of STL error: All data was not consumed
Exception building answer packet for hi.t.z/HINFO (All data was not consumed) sending out servfail
Environment
Operating system: CentOS 7.5.1804
Software version: pdns-4.1.5-1pdns.el7.x86_64
Software source: PowerDNS repository
Steps to reproduce
Create invalid HINFO RR: hi IN HINFO "a" "b" "c"
Try to use API or AXFR to get zone content, or dig HINFO hi.zone
Expected behaviour
a) it would be logical to expect that such RR will not pass validation when loading zone using pdnsutil
b) if, nevertheless, the incorrect data is provided by backend, it will be handled properly (log the problem and ignore extra content)
Actual behaviour
a) pdns silently dies on query of AXFR
b) API call produces "Internal server error" without any details
Short description
I had a zone file with an incorrect HINFO record:
hi IN HINFO "cpu" "os" "whatever"
The zone is loaded without any issues with pdnsutil load-zone, but attempt to retrieve zone content using API (/api/v1/servers/localhost/zones/t.z), or attempt to AXFR, or simple query for this RR produces errors:
HTTP ISE for "/api/v1/servers/localhost/zones/example.z": STL Exception: All data was not consumed
TCP Connection Thread died because of STL error: All data was not consumed
Exception building answer packet for hi.t.z/HINFO (All data was not consumed) sending out servfail
Environment
Steps to reproduce
hi IN HINFO "a" "b" "c"
Expected behaviour
a) it would be logical to expect that such RR will not pass validation when loading zone using pdnsutil b) if, nevertheless, the incorrect data is provided by backend, it will be handled properly (log the problem and ignore extra content)
Actual behaviour
a) pdns silently dies on query of AXFR b) API call produces "Internal server error" without any details