Looks like Verizon DNS can't resolve mikrotik.com. Flushed cache on router and MacBook. Switched to google DNS to fix. Anyone else having this issue? BTW, Verizon support response was:
Persistent DNS Resolution Steps
Manual DNS Configuration: As a temporary workaround, you can manually set your router or device to use Google DNS (8.8.8.8) or Cloudflare (1.1.1.1) to ensure uninterrupted access.
ONT Reset: Locate your Optical Network Terminal (ONT) and perform a power cycle by unplugging its power supply for 60 seconds. This can sometimes resolve deep-seated routing issues.
Advanced Support: If the issue remains, it may indicate a localized DNS propagation delay on the Verizon backbone.
I noticed issue in GitHub Action build, where it could not resolve download.mikrotik.com nor box.mikrotik.com at various times today. Changing some script curl/etc usage to resolve first using 1.1.1.1 seems to work than whatever GitHub (likely Azure then IDK) was using to resolve *.mikrotik.com.
But happen 30 minutes ago (~0000 UTC) in another GitHub project. So I'm not sure it's "fixed". Now perhaps TTL related... But TTL appears to 1h. Granted I'm reading TTL on my Mac, which does work to resolve, via Quad9 directly as DNS from Mac - so if fixed, IDK what the TTL might have been before....