aeden

Looks like there are some issues to resolve with the signup process and billing. I've contacted you via your support channel so we'll see how this works out. :-)

PMF = Product Market Fit

I am honestly curious why, when you learned lesson 1 (Lesson: Don’t quit your job too early), did you not apply it? Find a company in a completely different space, carve out your business in your contract, and work your job while you hone your product. In 3 to 5 years you may very well have a solid growing product, or not, but at least you won't be broke.

If the authoritative is using Anycast (which they should) then you run into similar problems that you get with Anycast resolvers, which is to say you might get different results depending on distribution of data. Due to this we currently provide an API for checking distribution of zone changes with our authoritative name servers: (https://developer.dnsimple.com/v2/zones/#checkZoneDistributi...).

FWIW, there is an IETF draft that may be suitable for addressing this: https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https...

Decentralized structured data store it seems. If you want a P2P application you have to store data somewhere. No idea if this fits the bill.

> but isn't well designed for more complex operations like handling large arrays of data, or writing custom code.

Even though they support writing Python and/or Javascript code in zaps? How is Paragon better at supporting writing custom code?

I've been learning about Firebase by building something for fun.

Just make sure you pick a ccTLD that has not already been bought/taken from the country in question. If you don't, it could be operated by Verisign anyhow (see .cc, .tv, etc)

DNSimple | Ruby & Go Systems Developer | Remote | Full-time | https://www.dnsimple.com

As a DNSimple Systems Developer, you are responsible for implementing new functionality, enhancing existing functionality, fixing issues, and developing an overall system to help achieve customer success through the automation of their domain management. We're a fully distributed team of experienced developers. Our systems are developed in multiple languages: Ruby, Go, Erlang. We deploy and operate our applications and infrastructure. We care about code quality and we adopt best practices to ensure maintainability. We test our code, we use code review, and we ship multiple times a day.

DNSimple provides simple, secure domain management automation for individuals and businesses of all sizes. DNSimple was created by developers for developers. Manage one domain or thousands of domains with our UI and API. Register domains, manage DNS zones, and automate issuance of Let's Encrypt certificates for your sites.

Full description: https://dnsimple.com/jobs#systems-developer

Email jobs@dnsimple.com to apply. Please mention you saw this comment on HN.

Thank you for the peer-base link. I've been investigating data storage on IPFS for application interop and I love the idea about using an existing library rather than re-inventing one. I will definitely be taking a closer look at this project.

I agree 100%. I'm a big fan of just calling them businesses.

They have a sort of FAQ on their shop page that provides info about this: https://thehelm.com/pages/shop

See under the question: What happens to my email if my power or Internet service goes out?

Registrars that are ICANN accredited are obligated to place all registrant data in escrow, so in effect, yes.

Intellectual property attorneys have fought the most to keep whois data public and accurate.

Those who buy and sell domains are another group who are annoyed that it is no longer public. They can easily solve the sell-side issue but when they want to buy a domain, if the owner is not specifically trying to sell it then it becomes more difficult to get ahold of them to make an offer.

Nice and succinct. This is exactly what I did for DNSimple.

DNSSEC support is increasing each year, but that's just one issue. DANE would also need to be implemented by browsers for full adoption, not just as a plugin to specific browsers.

Then again, I was responding to the question about an RFC or other standard, not whether it was feasible today. ;-)

DANE might provide a solution. See specifically the section https://tools.ietf.org/html/rfc6698#section-2.1.1, certificate usage 3:

3 -- Certificate usage 3 is used to specify a certificate, or the public key of such a certificate, that MUST match the end entity certificate given by the server in TLS. This certificate usage is sometimes referred to as "domain-issued certificate" because it allows for a domain name administrator to issue certificates for a domain without involving a third-party CA.

> But in this winner-takes-all reality, is that possible?

This is an assumption, and I would say, an invalid one. The reality is actually that there are many successful businesses in any given industry. This is thanks to the fact that one-size does not fit all. Niching down is a good way to build a small, profitable business, because you can address the needs of the niche better than those bigger players that have to try to solve the problems of many different customers using the same systems.

I've checked, it's definitely signed:

  ; <<>> DiG 9.11.0-P1 <<>> ed25519.nl +dnssec
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 594
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags: do; udp: 512
  ;; QUESTION SECTION:
  ;ed25519.nl.			IN	A
  
  ;; ANSWER SECTION:
  ed25519.nl.		1341	IN	RRSIG	A 15 2 3600 20171012000000 20170921000000 27662 ed25519.nl. Z62ywpWQ4ahOs0DZxIs3OAY67qc226z6rs8k8q2i/hdwQAjz5EL5ZJke t25LD88wx5kGY5ru6Dvfrd7KvODCAg==
  ed25519.nl.		1341	IN	A	77.72.150.82

  ;; Query time: 55 msec
  ;; SERVER: 8.8.8.8#53(8.8.8.8)
  ;; WHEN: Wed Sep 27 20:44:46 EDT 2017

If their servers were unresponsive, then a long TTL might help as caching resolvers would retry and eventually get a successful result. Based on the output of the OPs tests, they are responding with incorrect NXDOMAIN results. This means that resolvers will cache the NXDOMAIN result using the SOA negative result TTL.

You could remove the delegation entries for the name servers that are returning results though, that might help.

I see what you did there.

Thanks for linking this, it was quite an interesting lead.

Diversification perhaps? WEB clearly believes in the power of owning multiple businesses, perhaps he is just extrapolating from his own success that others are interested in following his lead?

Founder of DNSimple, author of the blog post, as well as the primary implementation author. I'll be happy to answer questions if you have them.

This is a bit different, and it's possible your registrar is not yet using the latest RAA (Registrar Accreditation Agreement). Specifically, the email you're talking about is the once-a-year verification email that all compliant registrars must send. The OP was dealing with a new rule which is part of the RAA 2013, which adds the requirement for verifying emails within 15 days of any registrant change that impacts either the name or the email address of the registrant.

(Edited to fix typo for RAA)

Don't use your home address in whois, period. Use a business address. If you have a site that is lucrative then you have enough to pay for a PO box or an office space. There are plenty of companies that will provide on demand office space and take and forward mail for a couple hundred dollars per month or less.

Dyn has no special role, they just provide DNS for a large number of high-traffic sites and services.

Slightly OT, but countries tend to dislike this brave new world where they cannot obviously and clearly collect taxes on business owners that reside in their country. It is going to be a tough day if the other shoe drops on this. No idea what it will look like if it happens though.

How about a combination of any other US bank + Transferwise? This is what I do (using Bank of America in the US). The transfers to Transferwise go through their US account (thus can be done as a no- or low-cost ACH) and the rates by Transferwise are pretty close to market rate.