- 1 General
- 2 Domains
- 3 Management
- 4 Selling
- 5 Software
- 6 Security
- 7 Free
- 8 DNS over HTTP
- 9 Alternate
- https://en.wikipedia.org/wiki/Multicast_DNS - mDNS, resolves host names to IP addresses within small networks that do not include a local name server. It is a zero-configuration service, using essentially the same programming interfaces, packet formats and operating semantics as the unicast Domain Name System (DNS). Although Stuart Cheshire designed mDNS to be stand-alone capable, it can work in concert with unicast DNS servers. The mDNS protocol is published as RFC 6762, uses IP multicast User Datagram Protocol (UDP) packets, and is implemented by the Apple Bonjour, Spotify Connect, Philips Hue, Google Chromecast, and open source Avahi (software) software packages. Android contains an mDNS implementation. mDNS has also been implemented in Windows 10, but its use is limited to discovering networked printers. mDNS can work in conjunction with DNS Service Discovery (DNS-SD), a companion zero-configuration technique specified separately in RFC 6763.
- https://en.wikipedia.org/wiki/ICANN - a nonprofit organization that is responsible for coordinating the maintenance and procedures of several databases related to the namespaces of the Internet - thereby ensuring the network's stable and secure operation. ICANN performs the actual technical maintenance work of the central Internet address pools and DNS Root registries pursuant to the Internet Assigned Numbers Authority (IANA) function contract.
- ICANNWiki - a nonprofit organisation dedicated to providing a community developed wiki on ICANN and Internet Governance. We specialize in outreach, engagement and accessibility. Our mission to "give everyone a voice in the future of the internet" by providing educational resources, workshops and building a strong sense of community.
- https://www.washingtonpost.com/news/the-intersect/wp/2015/02/23/the-surprisingly-complex-reason-you-never-see-emoji-urls/ 
- http://en.wikipedia.org/wiki/DNS_zone - any distinct, contiguous portion of the domain name space in the Domain Name System (DNS) for which administrative responsibility has been delegated to a single manager. A DNS zone is implemented in the configuration system of a domain name server. Historically, it is defined in the zone file, an operating system text file that starts with the special DNS record type Start of Authority (SOA) and contains all records for the resources described within the zone. This format was originally used by the Berkeley Internet Name Domain Server (BIND) software package, and is defined in RFC 1034 and RFC 1035.
The domain name space of the Internet is organized into a hierarchical layout of subdomains below the DNS root domain. The individual domains of this tree may serve as delegation points for administrative authority and management. However, usually it is furthermore desirable to implement fine-grained boundaries of delegation, so that multiple sub-levels of a domain may be managed independently. Therefore, the domain name space is partitioned into areas (zones) for this purpose. A zone starts at a domain and extends downward in the tree to the leaf nodes or to the top-level of subdomains where other zones start.
From DreamHost wiki;
- Forward mapping of hostname to an IP address (188.8.131.52).
- Forward mapping of hostname to an IPv6 address.
- Reverse mapping of an IP address (184.108.40.206) to a hostname (dreamhost.com).
- Mail eXchange records tell you which hostname to connect to for sending email.
- Say it, See Name, it points one domain name to another domain name, including mail service.
- Text records, these are free form text strings, used for things like SPF.
- Service records advertise a specific service a server offers. Zeroconf and XMPP Federation (Jabber and Google Apps) use SRV records in addition to PTR records.
- Delegates a domain or subdomain to another DNS server.
- xip.io - wildcard DNS for everyone. xip.io is a magic domain name that provides wildcard DNS for any IP address. Say your LAN IP address is 10.0.0.1. Using xip.io, [maybesomething.]10.0.0.1.xip.io resolves to 10.0.0.1. No configuration required! A free service from Basecamp.
- https://en.wikipedia.org/wiki/Name_server - a computer hardware or software server that implements a network service for providing responses to queries against a directory service. It translates an often humanly-meaningful, text-based identifier to a system-internal, often numeric identification or addressing component. This service is performed by the server in response to a service protocol request. An example of a name server is the server component of the Domain Name System (DNS), one of the two principal namespaces of the Internet. The most important function of DNS servers is the translation (resolution) of human-memorable domain names and hostnames into the corresponding numeric Internet Protocol (IP) addresses, the second principal name space of the Internet which is used to identify and locate computer systems and resources on the Internet.
- https://en.wikipedia.org/wiki/Root_name_server - a name server for the root zone of the Domain Name System (DNS) of the Internet. It directly answers requests for records in the root zone and answers other requests by returning a list of the authoritative name servers for the appropriate top-level domain (TLD). The root name servers are a critical part of the Internet infrastructure because they are the first step in translating (resolving) human readable host names into IP addresses that are used in communication between Internet hosts.
A combination of limits in the DNS and certain protocols, namely the practical size of unfragmented User Datagram Protocol (UDP) packets, resulted in a decision to limit the number of root servers to thirteen server addresses. The use of anycast addressing permits the actual number of root server instances to be much larger, and is 504 as of 17 January 2016.
- https://news.ycombinator.com/item?id=7839186 - list of good registrars
- http://www.ukreg.com/ - .co.uk - £2.95pa*com - £5.99pa.net - £9.49pa.eu - £8.89pa All
- https://www.namecheap.com - cheap. nameserver included.
- https://internetbs.net - cheaper. nameserver not included.
- http://www.domains.coop/ - .coop
- Git-based DNS Hosting - Steve Kemp
- http://www.1and1.co.uk/ - hmm, bibg corp, ugly ui
- http://123reg.co.uk - transfer out charges
- hidden transfer fees still?
- Network Solutions - avoid
- http://inessential.com/2014/01/21/network_solutions_auto-enroll_1_850 
Do NOT use GoDaddy. Google it +
- http://namevine.com/ - with social service lookup
- https://gigaom.com/2014/06/30/the-dark-side-of-io-how-the-u-k-is-making-web-domain-profits-from-a-shady-cold-war-land-deal/ [https://news.ycombinator.com/item?id=8587379
acronym in url, not domain - seo?
- http://uberdns.eu/ - uses git
# Quad9 nameserver 220.127.116.11 nameserver 18.104.22.168 # Provides: Security blocklist, DNSSEC, No EDNS Client-Subnet sent. nameserver 22.214.171.124 nameserver 126.96.36.199 # Provides: No security blocklist, DNSSEC, sends EDNS Client-Subnet. # Cloudflare nameserver 188.8.131.52 nameserver 184.108.40.206 # For IPv6: 2001:2001::, 2001:2001:2001::
# Google DNS nameserver 220.127.116.11 nameserver 18.104.22.168
- systemd-resolved is a system service that provides network name resolution to local applications. It implements a caching and validating DNS/DNSSEC stub resolver, as well as an LLMNR resolver and responder. In addition it maintains the /run/systemd/resolve/resolv.conf file for compatibility with traditional Linux programs. This file may be symlinked from /etc/resolv.conf.
- systemd-resolve — Resolve domain names, IPV4 and IPv6 addresses, DNS resource records, and services
See also #DNSCrypt
- https://github.com/kvz/nsfailover - Every minute (or whatever), nsfailover.sh checks to see if the primary configured nameserver can resolve google.com. If it cannot, it writes the secondary, or even tertary server to function as the primary server in /etc/resolv.conf
Servers, proxy, cache
- http://www.yadifa.eu/ YADIFA® is designed specifically for the efficient management of large Internet zones and uses dynamic updates to instantly change domain name records. It is equally optimised to handle multiple Internet zones. Our benchmark tests show how we measure up to the competition.
- Unbound is a validating, recursive, and caching DNS resolver.
- Dnsmasq provides network infrastructure for small networks: DNS, DHCP, router advertisement and network boot. It is designed to be lightweight and have a small footprint, suitable for resource constrained routers and firewalls. It has also been widely used for tethering on smartphones and portable hotspots, and to support virtual networking in virtualisation frameworks. Supported platforms include Linux (with glibc and uclibc), Android, *BSD, and Mac OS X. Dnsmasq is included in most Linux distributions and the ports systems of FreeBSD, OpenBSD and NetBSD. Dnsmasq provides full IPv6 support.
- pdnsd is a proxy DNS server with permanent caching (the cache contents are written to hard disk on exit) that is designed to cope with unreachable or down DNS servers (for example in dial-in networking). Since version 1.1.0, pdnsd supports negative caching.
- nscd - name service cache daemon
- DNSYO is a little tool I built to help me keep track of DNS propagation. In short, it's nslookup, if nslookup queried over 1500 servers and collated their results.
dig any domain.name show all records for domain
- http://network-tools.com/ - good all round domain/ip tool
- http://www.who.is/ - basic whois archive records
- iodine - lets you tunnel IPv4 data through a DNS server. This can be usable in different situations where internet access is firewalled, but DNS queries are allowed. It runs on Linux, Mac OS X, FreeBSD, NetBSD, OpenBSD and Windows and needs a TUN/TAP device. The bandwidth is asymmetrical with limited upstream and up to 1 Mbit/s downstream. 
- https://en.wikipedia.org/wiki/TSIG - Transaction SIGnature, protocol defined in RFC 2845. It is used primarily by the Domain Name System (DNS) to provide a means of authenticating updates to a DNS database. It is most commonly used to update Dynamic DNS or a secondary/slave DNS server. TSIG uses shared secret keys and one-way hashing to provide a cryptographically secure means of authenticating each endpoint of a connection as being allowed to make or respond to a DNS update.
still CAs, registrars and TLDs
- DNSCrypt is a protocol that authenticates communications between a DNS client and a DNS resolver. It prevents DNS spoofing. It uses cryptographic signatures to verify that responses originate from the chosen DNS resolver and haven't been tampered with.
- https://www.archlinux.org/packages/community/x86_64/dnscrypt-proxy/ - includes systemd service file to enable exec on start
sudo dnscrypt-proxy -R dnscrypt.eu-dk --local-address=127.0.0.1:40
Using dnsmasq listening on port 40 to cache requests. Also, edit dnsmasq.service to load after After=dnscrypt-proxy.service.
systemctl edit dnscrypt-proxy.socket
Note: The ListenStream and ListenDatagram options need to be cleared with empty assignment before overriding, otherwise the new address would be added to the list of sockets.
[Socket] ListenStream= ListenDatagram= ListenStream=127.0.0.1:40 ListenDatagram=127.0.0.1:40
- https://github.com/Cofyc/dnscrypt-wrapper - A server-side dnscrypt proxy which helps to add dnscrypt support to any name resolver.
- https://github.com/jedisct1/dnscrypt-proxy/blob/master/dnscrypt-resolvers.csv - Current list of free DNSCrypt-enabled resolvers
- DNSCrypt.eu does not censor or change DNS lookups, nor log your traffic through the DNSCrypt service in a way that can identify you.
- 22.214.171.124 and 126.96.36.199
- https://dnsleaktest.com - test dns connection
- Wikipedia:DNS-based Authentication of Named Entities (DANE) is a proposed protocol to allow X.509 certificates (commonly used for Transport Layer Security) to be bound to DNS names using Domain Name System Security Extensions (DNSSEC).
- FreeDNS - Free subdomain AND domain hosting!
DNS over HTTP
- https://github.com/fcambus/rrda - REST API allowing to perform DNS queries over HTTP
GNU Name System
- https://github.com/mwarning/KadNode - a small and decentralized DNS resolver that can use existing public key infrastructures. It utilizes the BitTorrent P2P network and mbedtls for TLS/crypto support. KadNode can intercept .p2p domain queries on the systems level and resolve them using a decentralized DHT network. TLS authentication can be used to make sure the correct IP address was found. If successful, the IP address is passed to the application making the request.