Closed Bug 656211 Opened 15 years ago Closed 15 years ago

Nameservers replying with fragmented UDP packets

Categories

(Infrastructure & Operations Graveyard :: NetOps, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ravi, Assigned: ravi)

Details

Attachments

(1 file)

A report came into abuse@ reporting 63.245.212.5 and 63.245.208.161 were sending UDP fragmented DNS replies to hosts in the 203.121.0.0 - 203.121.31.255 range. This appears to be consistent with revised draft to RFC 1035[1], Bigger Domain Name System UDP Replies, and specifically appears to be a byproduct of DNSSEC adding a lot of additional data in the response. I have attached a packet capture from my client with a DNSSEC query and a non-DNSSEC query of versioncheck.addons.mozilla.org which is one of the observed hosts that resulted in a UDP FRAG in a sample capture of ns1.mozilla.org. It is clear from the capture the DNSSEC reply is fragmented while the non is not. [1] http://tools.ietf.org/html/draft-ietf-dnsind-udp-size-02
Attachment #531549 - Attachment mime type: application/octet-stream → text/plain
Attachment #531549 - Attachment mime type: text/plain → application/octet-stream
Additionally the reply is larger because we are signing with 2 keys. We will eventually only sign with 1 key which should reduce the reply size, but we are almost certainly not going to be the only site which does this. Relaxing firewall filters to permit DNS UDP fragments is suggested since IPv6 will also introduce possible UDP fragments. Keeping this bug open for 24 hours.
OS: Mac OS X → All
Hardware: x86 → All
time's up!
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: