Ok, that clearly points to your home router which
- does not support edns
- does not support tcp dns
hence cannot handle payload bigger than 512 bytes.
The aljazeera’s answer is indeed bigger than usual however it would still fit 512 bytes if client would not request additional headers:
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 22780
;; flags: qr rd ra ; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; www.aljazeera.com. IN A
;; ANSWER SECTION:
www.aljazeera.com. 300 IN CNAME 2-01-3b91-0003.cdx.cedexis.net.
2-01-3b91-0003.cdx.cedexis.net. 20 IN CNAME www.aljazeera.com.edgekey.net.
www.aljazeera.com.edgekey.net. 21600 IN CNAME e9106.dscg.akamaiedge.net.
e9106.dscg.akamaiedge.net. 20 IN A 104.125.24.110
;; AUTHORITY SECTION:
;; ADDITIONAL SECTION:
;; Query time: 560 msec
;; SERVER: 10.0.0.158
;; WHEN: Mon Nov 20 20:23:26 2017
;; MSG SIZE rcvd: 255
which is 255 bytes.
I’d suggest setting up local dns cache - eg. unbound.