📄️ Requests & Responses
Requests and responses are the classes you'll most interact with in your handlers. Like Express, DinoDNS gives you access to the full request and response object for each handler in the chain. Modifications are allowed to both, allowing you to rewrite parts of the request or construct the response.
📄️ DefaultServer
The DefaultServer is the main underlying class that's responsible for receiving messages from the networks, constructing the plugin chain for incoming queries, and routing responses back to the client.
📄️ DinoDNS
The DinoDNS class is intended to be a high-level, lightweight abstraction on top of the base DefaultServer class. It accepts the same interface as DefaultServer, with the addition of optional parameters for each of the core plugin types: cache, store, and logger.
📄️ Networks
Networks are the interfaces handle deserializing queries and dispatching responses. Networks are responsible both for creating a listener over their underlying protocol, and deserializing messages out of the DNS wire format. As such, defining a network typically involves defining both the base Network interface, as well as a serializer.