application/dns-message

All MIME types
Application · Standards tree · RFC 8484header only

Media type / application

application/dns-message

A raw DNS wire-format message, as carried by DNS over HTTPS.

Served inline: Browsers have no renderer for this, so it downloads even without a Content-Disposition header. That makes it the quiet default for anything you do not want opened in place.

Browser behaviour

Downloads

Charset

no charset

Compression

Already compressed

Send it like this

Content-Type: application/dns-message

A binary payload has no character encoding. A charset parameter here is meaningless and occasionally confuses strict parsers.

Handling verdict

InlineDownloads

Browsers have no renderer for this, so it downloads even without a Content-Disposition header. That makes it the quiet default for anything you do not want opened in place.

Charsetno charset

A binary payload has no character encoding. A charset parameter here is meaningless and occasionally confuses strict parsers.

CompressionAlready compressed

The format compresses internally. Another transport encoding costs CPU on both ends and typically changes the size by less than a percent — sometimes upward.

NameStandards tree

Registered with IANA through a public review process, so the name is stable and every implementation can rely on it meaning the same thing.

Anatomy of the name

RFC 6838

Top-level type

application

Application

Subtype

dns-message

Registered in the standards tree.

Structured syntax

none

No suffix, so the payload format is defined entirely by the subtype itself.

Parameters

none

Beyond the charset rule above, this type defines no parameters of its own.

What trips people up

1 note
  • DoH requests and responses both use this type, which is what lets resolver traffic blend into ordinary HTTPS.

Response headers

Content-Type: application/dns-message
X-Content-Type-Options: nosniff
Content-Disposition: attachment; filename="example"

nosniff stops the browser second-guessing the type you declared, which is what makes the rest of this reliable. Content-Disposition: attachment names the saved file and removes any doubt about rendering.

Server configuration

route header

nginx

# application/dns-message has no file extension — set it on the route instead
add_header Content-Type "application/dns-message";

Apache

# application/dns-message has no file extension — set it on the handler instead
Header set Content-Type "application/dns-message"

Caddy

header Content-Type "application/dns-message"

Related media types

8
Familyapplication
Treestandards
Suffix
Inlinedownload