The 65 HTTPS record in particular is now frequently requested by Chrome
and without this mapping defined an error is thrown.

If an error is thrown while creating a Request object, such as when an
unknown resource record type is requested, there's no way for the client
to handle it. The error is thrown before the request is emitted and the
handler is called. This change leaves the underlying error throwing as
it is but catches the error in the server and emits them instead.

Any errors that might be emitted from the socket rather than the server
can't be handled by the client. This listens for errors on the connection
(and request and response) and emits them from the server.

In order to do that, the Request and Response objects (which inherit from
DNSMessage) must actually be EventEmitters. They often call emit, but only
in rare code paths. Those code paths would throw because emit wasn't a function.