@Jackobli @letsencrypt We don't delay. We collect all update tasks and prioritize them based on your payment status and other factors. The time range to publish you can expect is listed under "Sync time" on https://t.co/oD1GXVlXrg
@juanjobnt Only as long as BuddyNS can reach the old address for AXFR. In most cases, you need to delete and re-add the zone on BuddyNS with the new IP address. Shouldn't happen often; otherwise see https://t.co/VFq6FcWBXy
@PGregg@EricLoyd@BuddyNS Mostly correct, and we recommend puck too :) As a word of notice: many resolvers pick which NS to ask based on prior response times, which causes load not to be equally distributed among your NS servers. Some more help at https://t.co/LefPApqQ7m
@PGregg@BuddyNS@EricLoyd We count aggregates per-account on edge nodes in real-time, as each query comes in. Users who pay for GeoStats also have per-zone traffic metrics, which require moving around much more data. Done ex-post, manual log analysis is required, as explained in the FAQ.
@FrankFshagan You find a guide to our API with "curl" examples @ https://t.co/mfaEd0miHi and an interactive OpenAPI guide with JSON examples @ https://t.co/OcP9gsAnbb . No official DA plug-in at the moment. May I ask you your reason to drop cPanel? Thanks!
@retsamtsop@dnsflagday kills support for abnormal implementations of some EDNS responses. BuddyNS (and others) reject EDNS altogether, so resolvers are fine. ISC's tool tests support for EDNS commands, so its result is misleading for @dnsflagday .
@retsamtsop@dnsflagday kills support for abnormal implementations of some EDNS responses. BuddyNS (and others) reject EDNS altogether, so resolvers are fine. ISC's tool tests support for EDNS commands, so its result is misleading for @dnsflagday .
@BastienChong@BuddyNS We did reply via e-mail, and reached over via SMS when we suspected you weren't receiving :) Please use @BuddyNSsupport for support. Thanks!