npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

nodedns

v1.0.1

Published

An implementation of the DNS protocol.

Downloads

10

Readme

nodedns

This is a server implementation of the DNS protocol.

Useful information

Usage

const nodedns = require('nodedns');

const server = new nodedns.DNSServer(function(req, res) {
	var record = new nodedns.DNSMessageResource();
	
	// Name: www.example.com
	record.name = nodedns.DNSDomainName.fromLabels(['www', 'example', 'com']);
	
	// Record type: A
	record.type = 1;
	
	// Record class: IN
	record.rclass = 1;
	
	// TTL: 1 hour
	record.ttl = 3600;
	
	// Data: 127.0.0.1
	record.data = new Buffer([127, 0, 0, 1]);

	// Add record to 'answers' section of the response message
	res.answers.push(record);
	
	// Send response
	res.send();
});

server.listen(53);

Messages

Both requests and responses come in the form of DNSMessage instances. DNSMessage contains the following fields:

  • header: DNSMessageHeader
  • questions: DNSMessageQuestion
  • answers: DNSMessageResource[]
  • authorities: DNSMessageResource[]
  • additionals: DNSMessageResource[]

Question structure

Requests typically contain 1 question in the questions array of the DNSMessage. This question contains the following fields:

  • qname: DNSDomainName
  • qtype: Number
  • qclass: Number

Domain names

Domain names are represented by DNSDomainName. Instances of the class contain an array of labels.

To quickly convert a DNSDomainName to a readable domain one can use domain.labels.join('.')

There are two ways of creating a DNSDomainName:

// From an array of labels
var domain = nodedns.DNSDomainName.fromLabels(['www', 'example', 'com']);

// From a string representation
var domain = nodedns.DNSDomainName.fromString('www.example.com');

Resources

Resources or records are represented by DNSMessageResource objects. A DNSMessageResource contains the following fields:

  • name: DNSDomainName
  • type: Number
  • rclass: Number
  • ttl: Number
  • rdlength: Number (This is ignored when encoding messages)
  • rdata: Buffer