Why is netcups DNS so slow?
-
NetCup here too and renewing Certificates via their API took AAAAGESSSSS
I bet their standard excuse is again: We are cheap...
-
First response, translated via deepl.com
"Thank you very much for your inquiry.
I have just forwarded your inquiry to our colleagues in the relevant department for further consideration.
We therefore ask for your patience. We will get back to you as soon as possible.Yours sincerely,
netcup team" -
Having used all manner of VPS provider over the years, as well as domain name registrars, I can confidently tell you sometimes DNA propagation is slow, sometimes it isn't. Sometimes there is a reason, sometimes there isn't. Sometimes, if you bought your domain from the same provider from whom you bought/rent a VPS, that provider will artificially slow things down to try to get you to "upgrade" (hence never buying a domain from the VPS provider). Sometimes providers give you a Time-to-Propagate option (1 min, 5 min, 1 hr, 6 hr) which many users overlook, sometimes they don't. If you use a provider which is known enough to be slow it's in the documentation of other companies, then that's what you have to work with. For me, waiting for DNS propagation is the perfect time to sit back and read the manuals, or google the app I just installed to learn a bit more, or peruse the Forums. Sometimes it goes quicker than I expected, but generally I don't expect to be up and running immediately. I've found that including that in my mental processing of self-hosting diminishes stress.
-
I tend to avoid the Netcup DNS service since it has always been super slow, not even to propagation, just the change on their end.
Maybe they set some high internal TTL for every record?
-
@scooke our experiences are the opposite! I’ve never had to wait for dns propagation when installing new apps. For me, it’s up immediately. I’ve only had to wait when purchasing a new domain or setting up a new VPS. Unless I misread your post and in that case ignore mine
My provider list is Contabo, name cheap, name silo, porkbun, cloudflare, and bunnydns.
-
@humptydumpty Well, using my regular Wildcard setup, once the A records are entered for a given domain which is then added to the Cloudron, then, yes, there is no delay when installing an app on a subdomain. But when I add a new domain to Cloudron I usually have to wait 5 min to 12 hours for the various DNS records to propagate from the registrar before Cloudron picks it up. I move domains in and out of Cloudron often, and use(d) Porkbun, Spaceship, Namecheap, Namesilo, and Dynadot, Netcup, Gandi, Fullhost, Name.com, Cloudflare. As I wrote, it's been consistently like this that once I enter the A records (and whatnot) for a domain to point to wherever, I just walk away and go do something else while I wait for the propagation.
A life lived in fear is a life half-lived
-
@scooke said in Why is netcups DNS so slow?:
Wildcard
I'm using the programmable DNS (CF and Bunny). Maybe that's why it's faster.
It's not something we control or having inside info on.
