Never you mind le comments section below, et jamais you mind le previous answers in le edit history. After about an hour of certains conversation avec friends (thank you @joeQwerty, @Iain, et @JourneymanGeek), et certains jovial hacking around we got to le bottom of les deux votre question et le situation on le whole. Sorry for brusqueness et misunderstanding le situation completely at first.
Let's step through le process:
You buy wesleyisaderp.com at, let's say, NameCheap.com.
Namecheap as votre registrar will be où you populate votre NS records. Let's say you actually want to host le DNS zone on Digital Ocean.
You point votre shiny nouveau domain's NS records to ns1.digitalocean.com et ns2.digitalocean.com.
Cependant, let's say J'étais able to determine that you had registered that domain, and furthermore that you had changed votre NS records to Digital Ocean's. Then I beat you to a Digital Ocean account et added le zone wesleyisaderp.com to mon own.
You essayez de add le zone in your account mais Digital Ocean says that le zone déjà exists in leur system! Oh noes!
I CNAME wesleyisaderp.com to wesleyisbetterthanyou.com.
Hilarity ensues.
Some friends et I juste played this exact scenario out, et yes it works. If @JoeQwerty buys a domain et points it to le Digital Ocean nameservers, mais I déjà had that zone added to mon account, alors Je suis le zone master et can do avec it what I want.
However consider that someone would have to premier add le zone to leur DNS account, et alors you'd have to point votre NS records to le name servers of that même host for anything nefarious to happen. De plus, as le domain owner, you can switch NS records tout time you want et move le resolution away depuis le bad zone host.
The likelihood of this happening is a bit low to say le least. C'est said that, statistically, you can shuffle a deck of 52 playing cards et get an ordering that no autre human has ever gotten, et no autre human ever will. Je pense le même reasoning exists here. The likelihood of someone exploiting this is so très low, et there are better shortcuts in existence, that it probably ne va pas happen in le wild by accident.
De plus, si you own a domain at a registrar et it someone happens to have made a zone on a provider like Digital Ocean that you collide with, Je suis sure si you provide proof of ownership, they'd ask le person who made le zone in leur account to remove it depuis il y a no reason for it to exist as they're pas le domain name owner.
But what about A records
The premier person to have a zone on, par exemple Digital Ocean, will be le one that controls it. You cannot have multiple identical zones on le même DNS infrastructure. So par exemple, using le silly names above, si J'ai wesleyisaderp.com as a zone on Digital Ocean, no one else on Digital Ocean's DNS infrastructure can add it to leur account.
Voici le fun part: I actually really have added wesleyisaderp.com to mon Digital Ocean account! Go ahead et essayez de add it into yours. It ne va pas hurt anything.
So en conséquence, you ne peut pas ajoutez unn A record to wesleyisaderp.com. C'est tous mine.
But what about...
As @Iain pointed out below, mon point #4 ci-dessus is actually too verbose. Je ne have to wait ou plot ou scheme at all. I can juste make thousands of zones in an account et alors sit back et wait. Technically. If I make thousands of domains, et alors wait for them to get registered, et alors hope they use le DNS hosts that J'ai set mon zones on... maybe I can do something kinda bad? Maybe? But probably not?
Apologies to Digital Ocean & NameCheap
Note that Digital Ocean et NameCheap are pas unique, et have nothing to do avec this scenario. Ceci est normal behavior. They are blameless on tous fronts. I juste used them depuis that was le example given, et they're très well known brands.
