Was it really a block at the registrar level or was it a block at the DNS level, i.e., the registrar also ran DNS service and their DNS service refused to return responses for zoho.com domains?
At what layer or at which stage of the protocol can a registrar disrupt this and take a domain offline?
ns1.vtitan.com
pdns90.ultradns.net
pdns90.ultradns.com
dns1.p03.nsone.net
dns2.p03.nsone.net
nds3.p03.nsone.net
Those don't appear to be connected to the registrar (tierra.net); most likely the NS records were removed or replaced with servers that direct all queries to a parking page for abusive domains. The TLD servers for com. return a 2 day TTL for all glue records, and their SOA record indicates a 1 day negative TTL.(Of course, some caching resolvers ignore TTLs :( )
Terms:
ICANN: The organization responsible for coordinating the maintenance of the domain name system (among other things).
Registrar: A company authorized to update ICANN database on behalf of registrants. Google, GoDadddy, Enom, etc are registrars
Registrants: An entity that wants to register a domain name. In this case, Zoho is a registrant, but it could also be an individual. This is your role if you 'own' a domain.
Authoritative Name Server: A domain name server that is considered authoritative for a specific domain.
Stuff registrars can do (among other things):
1.) They can update the ICANN database to disable a domain completely[1]
2.) They can replace your authoritative name servers with their own or someone else's (ex: botnet domains being reassigned to a security company for dismantling via court order)[2]
3.) If the authoritative name servers for a domain are owned by the registrar, then the registrar can merely change the DNS entries themselves to point to something other than the domain owner's wishes.
[0] - https://en.wikipedia.org/wiki/ICANN
[1] - https://www.icann.org/resources/pages/epp-status-codes-2014-...
[2] - https://www.icann.org/en/system/files/files/guidance-domain-...
what in the world?