I already checked out ClouDNS, but their plans are a bit expensive.

If you're OK with DNS providers (who in general seem to be better at providing APIs than the your typical registrar), do consider ClouDNS.net (@BoyanPeychev is not active here any more it seems). A so

In the last 8 years, internet.bs has been the only one without a single trouble (for me, of course). They offer interesting prices, dynamic DNS and allow external domains.

I was bored, and made a discord bot for a private server of mine, and only me in it and i just update dns, and order domains from discord. (sloppy coding, but it works)

I did really love using LunaNode when I had a VPS with them, I'll definitely consider them for DNS hosting if I ever need another VPS from them.

lunanode does DNS, also with an API

I've looked into managed DNS services but all of them are pretty expensive if you go above 100 records. I've never used DO before and $60/year for DNS hosting doesn't sound like a good deal, if I ever

Listing current DNS recordsAdding DNS recordsUpdating DNS recordsRemoving DNS recordsListing current DS (DNSSEC) recordsAdding DS (DNSSEC) recordsDeleting DS (DNSSEC) records

Edit: Hmm, if it's just about DNS, can't you just use a DNS provider with a decent API, separate from your registrar? From what I've heard, DigitalOcean has a pretty good API.

I need to be able to add or remove a single DNS record using the API but this is unfortunately not possible with Namecheap so I need to look elsewhere. Any recommendations for an ICANN accredited reg

* Any other VM will connect to portgroup at vswitch1 and use router VM eth1 IP address as their gateway (and usually DNS).

(Quote)

Both your traffic and DNS requests would go through it.

you can limit the dns for your ISP ASN/IPRange. if you got static IP, you only need to whitelist that ip

Edit : Gave that issue a quick read. I never thought that people will target open DNS servers, but it does make sense (Image)

DNS-over-TLS use 853 port.

(Quote)

(Quote)

(Quote)

Depending on how you have things setup, usually you can have an internal (within the home/LAN) DNS forwarder (like dnsmasq) which listens on port 53 from clients, but forwards requests to another serv