A RFC Compliant Verified DNS server
High Assurance DIDs with DNS
This document outlines a method for improving the authenticity, discoverability, and portability of Decentralized Identifiers (DIDs) by utilizing the current DNS infrastructure and its technologies. This method offers a straightforward procedure for a verifier to cryptographically cross-validate a DID using data stored in the DNS, separate from the DID document.
Serving DNS using a Peer-to-Peer Lookup Service
Download Citation | Serving DNS using a Peer-to-Peer Lookup Service | The current domain name system (DNS) couples ownership of domains with the responsibility of serving data for them. The DNS security extensions... | Find, read and cite all the research you need on ResearchGate
Useful utilities and toys over DNS
Free and useful services over DNS accessible on command line
FOSDEM 2024 - Domain: A modular Rust DNS toolkit
The "domain" crate is a Rust library that aims to provide a wide range of building blocks that are necessary or useful when building specialised DNS applications.
rfcs/atproto/001-private-content.md at main · knasher/rfcs
Technical RFCs and design proposals for protocols and systems - knasher/rfcs
Dynamic DNS (DDNS) for Home Server and VPS etc, Free!
Free Dynamic DNS (DDNS) by POP3,IMAP4,FTP,HTTP-BASIC for Home Server, Webcam, VPS. You can use many free sub domain, .jp, .net, .asia, etc.. DynDNS is not free
DNS Filtering Services: Security & Network Protection | Control D
Control D's DNS filtering software blocks unwanted websites, prevents malware, enforces web policies, and strengthens network security in minutes.
Introducing Nomulus: an open source top-level domain name registry
DNS-Anchored Durable Identity for AI Agents (DNSid)
Autonomous software agents are being deployed across enterprise, cloud, and cross-organizational boundaries. These agents negotiate, transact, delegate, and produce work products that persist beyond their own ephemeral runtime. Current standards and initiatives for agent identity collectively address runtime authentication, authorization, lifecycle management, and tool interaction, but a gap remains: a durable, governance-backed identifier that lets a relying party determine and verify the accountable entity behind an agent it encounters, including agents that have since been retired or whose keys have rotated, and attribute past and present work products to that entity. Lifecycle-history verification is governed by the applicable log method and deployment scope. DNSid addresses the accountable layer of identity: the durable ownership anchor that existing agent identity standards do not provide. This document specifies DNSid, a minimal identity primitive that assigns each agent a Fully Qualified Domain Name (FQDN), binds it to an accountable entity identified by a DNS domain under that entity's control, and publishes a structured set of pointers in DNS TXT records to the agent's cryptographic keys, lifecycle log, and operational status. DNSid uses accountable-entity-controlled signatures for record integrity and an abstract append-only lifecycle log for history. It is designed to sit beneath existing identity, authentication, authorization, and agent interaction standards without competing with them. DNSid introduces no new DNS resource record types, opcodes, or response codes, and requires no changes to DNS resolvers, authoritative servers, or the DNS protocol. It applies to any agent that can be assigned an FQDN whose accountable entity can publish verification material; public discoverability of the agent is not required.
Special-Use Domain Names
This document describes what it means to say that a Domain Name (DNS name) is reserved for special use, when reserving such a name is appropriate, and the procedure for doing so. It establishes an IANA registry for such domain names, and seeds it with entries for some of the already established special domain names.
w3c-cg/udna
This repository holds the work of the W3C Universal DID-Native Addressing (UDNA) Community Group. We are developing a standard for addressing Decentralized Identifiers (DIDs) on the web.
The purpose of DNS is to spread scams
I imagine everyone here has received an unsolicited message telling them that their tax is overdue and that they urgently need to visit Genuine-Tax-Payment-Website.fart or that a parcel is delayed at customs and you can pay a small sum for its release at Almost-The-Right-Acronym.ak You know it is a scam. Most people just mark as spam and move on with their day. But a significant number of people …
I've been pondering about having the browser resolve at:// URLs. I have been thinking that we could introduce a DNS-like (maybe DNS itself?) entity that goes from did:plc to URLs, the same way DNS goes from names to IP, and have the browser depend on that similar to how it depends on a DNS server.
