3 ms·

Thanks for your comment. The DNS is used for a lot more than converting domain to IPs and mail servers, run: dig target.com TXT And be amazed at the pollutio

Thanks for your comment. The DNS is used for a lot more than converting domain to IPs and mail servers, run: dig target.com TXT And be amazed at the pollution at the apex. SPF, DMARC and others show that DNS is already being used for much more. The DNS is a distributed database. The primary key is the domain and we believe that converting human friendly domains to machine readable data shouldn’t stop at IPs, mail servers and anti-spam measures (SPF and DMARC). It should extend to phone numbers, gps coordinates, bank details and more.

potamic 5y ago
That is indeed quite some bloat. I suppose it makes sense for use cases where domain name related metadata is needed across the internet infrastructure (like for email with SPF). Just not sure it's a good idea to extend DNS for data like contact info that is ultimately meant for human consumption. Where do we draw the line otherwise? I could start caching web artefacts in TXT records or even serve entire web pages.
- elliottinvent 5y ago
  I agree there’s a line where putting data in DNS is just a gimmick (eg storing images in DNS) because the web does it infinitely better. But in the case of contact information I think it makes a lot of sense. This demo site is an intense example because it’s contact info for very large companies. For smaller companies it’s just one DNS TXT record, usually under the original 512b DNS UDP packet limit. I don’t agree that contact information is meant for human consumption. The humans (or often machines) at the end of phone numbers are for humans but the route to get there (eg telephone system) is designed for machines.