Warning: Message parser reports malformed message packet.
See original GitHub issueHello,
When i execute : “dig wbc.weble.ch +trace”
I’ve this result :
; <<>> DiG 9.10.3-P4-Raspbian <<>> wbc.weble.ch +trace
;; global options: +cmd
. 72776 IN NS e.root-servers.net.
. 72776 IN NS f.root-servers.net.
. 72776 IN NS g.root-servers.net.
. 72776 IN NS h.root-servers.net.
. 72776 IN NS i.root-servers.net.
. 72776 IN NS j.root-servers.net.
. 72776 IN NS k.root-servers.net.
. 72776 IN NS l.root-servers.net.
. 72776 IN NS m.root-servers.net.
. 72776 IN NS a.root-servers.net.
. 72776 IN NS b.root-servers.net.
. 72776 IN NS c.root-servers.net.
. 72776 IN NS d.root-servers.net.
;; Received 811 bytes from 172.16.1.1#53(172.16.1.1) in 3 ms
ch. 172800 IN NS a.nic.ch.
ch. 172800 IN NS b.nic.ch.
ch. 172800 IN NS c.nic.ch.
ch. 172800 IN NS d.nic.ch.
ch. 172800 IN NS e.nic.ch.
ch. 172800 IN NS f.nic.ch.
ch. 172800 IN NS g.nic.ch.
ch. 172800 IN NS h.nic.ch.
ch. 86400 IN DS 11896 13 2 24EE6537B1C452D3AEBF439DCF74024717054152DA7F206D5FCBA1A9 0F70711F
ch. 86400 IN RRSIG DS 8 1 86400 20190930050000 20190917040000 59944 . kaGRIHYMMuruHaWAIHb9kVXZNH9tzDNkqgQcX9oFotbd86puoY6/sRp6 +y8lhBxUgm7qi7GM3JxTZ3iZ3/dpgNv7PTVLskDUwrscSQC5jkxzOzvB 5oo59keBmC9X2UlJ+rLJoLNLNuao+6LyMPZtSgW7DudvN1rMQpZM39is XuG5URCG9qSBzkJt3FPESMBT+h356sbvN4Jz8GvwPLaE2mpdNnuBwAIG qBYaqDiWhE0pLuSVwdLlPftCnJ7RT1dNfTI3wJfSl2fDI6TpHPgr8bSt 4H5HDutqvsZuTQp1p2CqKLtAJOCIKBPOfact7SyYaVFlmuqhQMZLwFDP UnZDiQ==
;; Received 860 bytes from 193.0.14.129#53(k.root-servers.net) in 11 ms
weble.ch. 3600 IN NS ns1.switchplus.ch.
weble.ch. 3600 IN NS ns2.switchplus.ch.
HS53IQDLBM00MIRD1LPS0J47BPJP5SF8.ch. 900 IN NSEC3 1 1 2 87E195EB HS63KNDB8F15206UBJQDIRIISQ1EK7N7 NS SOA RRSIG DNSKEY NSEC3PARAM
HS53IQDLBM00MIRD1LPS0J47BPJP5SF8.ch. 900 IN RRSIG NSEC3 13 2 900 20191013161405 20190913160114 7967 ch. GZsRnHBemsdnY1WI6R9+O9NjL9a7s479t3Oqcw6j28LVsYZWOjqUPnSK bjRHaSKp4hZrtxX9gMzIRAJChgL3AQ==
LBHUG80GC3VGPEU435F60L91DBJ3LJE8.ch. 900 IN NSEC3 1 1 2 87E195EB LBK2U02LTLKUCOCKTKJG1O2EMMOK0HBB NS DS RRSIG
LBHUG80GC3VGPEU435F60L91DBJ3LJE8.ch. 900 IN RRSIG NSEC3 13 2 900 20191010205442 20190911113001 7967 ch. UdhiNXu1UZx2JE1qg/WI+I51OMtCanyanuqtArGcuMc+GyFZR7NeLK9l GpMKl5wmdz3EDm+TL+y8X7XWncNf8w==
;; Received 487 bytes from 194.146.106.10#53(f.nic.ch) in 13 ms
wbc.weble.ch. 3600 IN NS ns1.weble.ch.
wbc.weble.ch. 3600 IN NS ns2.weble.ch.
;; Received 109 bytes from 193.223.77.3#53(ns2.switchplus.ch) in 119 ms
**;; Warning: Message parser reports malformed message packet.**
wbc.weble.ch. 300 IN A 213.193.121.210
;; Received 67 bytes from 213.193.121.211#53(ns1.weble.ch) in 31 ms
Here the response object :
var response = new dns.Packet(request);
response.header.qr = 1;
response.answers.push({
name: oDomain,
address: target.target,
type : dns.Packet.TYPE.A,
ttl : ttl,
class : dns.Packet.CLASS.IN
});
And in console I’ve:

Is there a link between this error and the warning ;; Warning: Message parser reports malformed message packet. ?
Is there something wrong ?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Warning: Message parser reports malformed message packet.
Warning : Message parser reports malformed message packet. I've Been having intermitte issues where I'm no longer able to access certain websites like...
Read more >Message parser reports malformed message ... - Google Groups
Hi,. I'm having issues trying to resolve www.sondait.tasker.com.br. The result from dig +trace is as follows:.
Read more >Error msg: ;; Warning: Message parser reports malformed ...
It started a few weeks ago and it's intermittent. Going to google.com,Facebook.com would return. This site can't be reached www.google.com's ...
Read more >[Pdns-users] Message parser reports malformed message ...
Warning : Message parser reports malformed message packet. "Served by POWERDNS 2.9.19 $Id: packethandler.cc 518 2005-10-16 15:36:51Z ahu $"
Read more >Error msg: ;; Warning: Message parser reports malformed ...
Error msg : ;; Warning : Message parser reports malformed message packetHelpful? Please support me on Patreon: ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

That’s because the encoder for that packet type doesn’t exist in dns2.
Check my PR on gitlab for a more in-depth explanation.
TL;DR: This mostly (exclusively?) happens when the DNS client sends edns queries (DNS with some crypto auth request attached).
This happens when dns2 tries to answer to a request it did not understand (mostly OPT RR). The solution in my case was to filter out unsupported types from prepared responses.