Error [protocol]: Malformed packet when querying TXT records
tjoanp opened this issue · 2 comments
tjoanp commented
dog v0.1.0
Windows 10 2004
When quering some domains for TXT records, dog only responds with Malformed packet:
dog gp.se TXT
Error [protocol]: Malformed packet: length 351 was specified, but read 7 bytes
dog svt.se TXT
Error [protocol]: Malformed packet: length 301 was specified, but read 237 bytes
dog kungalv.se TXT
Error [protocol]: Malformed packet: length 378 was specified, but read 172 bytes
dog kungalv.se TXT @1.1.1.1
Error [protocol]: Malformed packet: length 378 was specified, but read 172 bytes
dog kungalv.se TXT @8.8.8.8
Error [protocol]: Malformed packet: length 378 was specified, but read 172 bytes
Although most other domains I've tested works fine, for example
dog one.se TXT
TXT one.se. 30m00s "v=spf1 redirect=_spf.one.se"
and other types of records seems to be no issue:
dog kungalv.se MX
MX kungalv.se. 59m51s 10 "kungalv-se.mail.protection.outlook.com."
A kungalv-se.mail.protection.outlook.com. 1s + 104.47.0.36
A kungalv-se.mail.protection.outlook.com. 1s + 104.47.1.36
ogham commented
This is issue #18, which has been fixed in development (I tried your examples and it works now) but is not yet released. With luck there will be a v0.2.0 release soon.
ogham commented
(If you want to know the reason why some work and some don't, it's due to the way TXT records longer than 255 bytes are encoded.)