Re: [VoiceOps] DIDWW API DNS Issue

2022-01-21 Thread Mike Johnston
Losing millions of dollars. Very nicely said. Then there are those that move their website, with their DNS, to a different provider, and are then confused as to why their email is broken. Of course it is the email providers fault, and they have no comprehension that it might somehow be relat

Re: [VoiceOps] DIDWW API DNS Issue

2022-01-20 Thread Alex Balashov
That’s all good and fine for your DNS, but it did nothing for me when Peter from www.BeckmanPimpsStereos.com was calling every 3 minutes screaming that his web site has been down for a day and that he’s losing “millions of dollars”, all because we just had to migrate his ColdFusion site off a ye

Re: [VoiceOps] DIDWW API DNS Issue

2022-01-20 Thread Peter Beckman
Hahaha yeah, thanks Residential ISPs, your DNS sucks. I always found a better caching resolver, like UUNET, until Verizon got better at it, and then Google DNS came along. The caches have cleared. Beckman On Thu, 20 Jan 2022, Alex Balashov wrote: Why, back in my day, residential ISPs would ign

Re: [VoiceOps] DIDWW API DNS Issue

2022-01-20 Thread Alex Balashov
Why, back in my day, residential ISPs would ignore your TTLs and cache for 3 days no matter what you did… Kids these days. — Alex > On Jan 20, 2022, at 7:54 PM, Peter Beckman wrote: > > Please, y'all -- when doing a DNS migration, ensure 1000% that your DNS > records on your old DNS provide

[VoiceOps] DIDWW API DNS Issue

2022-01-20 Thread Peter Beckman
DIDWW seems to be midway between moving from GoDaddy DNS to their own internal DNS. Their DNS Servers are cached for 1 hour. We started seeing DNS failures for api.didww.com which returns no entries from ;; AUTHORITY SECTION: didww.com. 3600IN NS ns14.