Hacker News Reader

Comment by tao_oat | Hacker News Reader

I'm using Bunny DNS and it's been mostly unremarkable (which is a very good thing for a DNS provider)!

The only annoyance is that their domain import auto-detects existing records, but it seems to miss a lot of them so you end up manually copying a lot of things over anyway.

View on HN

In their defence, nobody can implement auto-detecting domains well, because there's no way to efficiently enumerate DNS records.

(Excluding NSEC-style enumeration, which is not always available.)

I feel like I'm missing something, AXFR?

Almost no mainstream existing provider you’re migrating from would support AXFR from Bunny’s servers. But yes, AXFR would be the ideal solution in a perfect world.

iirc at least some providers let you whitelist AXFR for migrating away from them, but seems like it is usually only if you pay enough (i. e. restricted to enterprise plans).

Since it's much rarer than I thought, I guess it makes sense bunny haven't implemented support for ingesting with AXFR.

AXFR is not supported by AWS Route 53, Google Cloud DNS, Azure, Rackspace, Hetzner, Bunny, Alibaba Cloud DNS, No-IP, nor Tencent.

It is supported by Akamai Edge DNS, Oracle Cloud, enterprise Cloudflare accounts, IBM NS1 Connect, ClouDNS, CloudFloorDNS, and DNS Made Easy.

That's not their fault, though. There's no perfectly reliable way to enumerate the DNS records for a particular domain.

I'm a BunnyDNS user and wanted to share a warning - the import from a zone file can drop records silently, and the export will fail to export some of your records. I reported bugs some months ago, they replied they've fixed some but it's still a problem.

Spirit: ensure you keep a good copy of your zone files (bind format), their import / export has issues (it also doesn't include SOA or NS records). I spent time (before the recent fixes) manually validating records.

Reply on news.ycombinator.com