On 10/5/21 14:08, Jean St-Laurent via NANOG wrote:
Maybe withdrawing those routes to their NS could have been mitigated by having NS in separate entities.
Well, doesn't really matter if you can resolve the A/AAAA/MX records, but you can't connect to the network that is hosting the services.
At any rate, having 3rd party DNS hosting for your domain is always a good thing to have. But in reality, it only hits the spot if the service is also available on a 3rd party network, otherwise, you keep DNS up, but get no service.
Mark.