101–109 of 109 posts
Earlier quoted context omitted.
Just because it's doing key-value pairs does not mean it's DNS. If I can't `dig` it, it's not DNS. This is simply doing HTTP redirects and works with no other protocols.
Hm, there are plenty of DNS records (not to mention all the custom ones all around the world) that you won't be able to `dig` but most people would still call DNS.
Its incredible how insane this seems from the title but how practical it sounds from the readme..
This may be a little off topic, but has anyone ever considered a web standard that includes a cryptographic signed file in a standard "well known" location that would contain content such as - Domains used by the site (first party) - Domains used by the site (third party) - Methods allowed per domain. - CDN's used by the site - A records and their current IP addresses - Reporting URL for errors Then include the publi…
That's a good use case for blockchain, in regards to the "consensus aggregation of data" that you mentioned.
Earlier quoted context omitted.
Hm, there are plenty of DNS records (not to mention all the custom ones all around the world) that you won't be able to `dig` but most people would still call DNS.
Can you provide an example of one that you can't 'dig'? I have my doubts.
So seems to be a proper DNS record, but I can't make it work with dig.
Earlier quoted context omitted.
Can you provide an example of one that you can't 'dig'? I have my doubts.
One example: I can't seem to get dig to work with URI records (but I might be missing some flag). Doing `dig URI _kerberos.hasvickygoneonholiday.com` returns "no servers could be reached" while doing `kdig URI _kerberos.hasvickygoneonholiday.com` returns the proper records. So seems to be a proper DNS record, but I can't make it work with dig.
Earlier quoted context omitted.
One example: I can't seem to get dig to work with URI records (but I might be missing some flag). Doing `dig URI _kerberos.hasvickygoneonholiday.com` returns "no servers could be reached" while doing `kdig URI _kerberos.hasvickygoneonholiday.com` returns the proper records. So seems to be a proper DNS record, but I can't make it work with dig.
Plain old "dig" works for me! I suspect it may be an older version of dig you're using? This is DiG 9.11.5-P4-5.1ubuntu2.1-Ubuntu on Ubuntu 19.10 ...