The necessity of this, the price for which it is offered and all those other matters aside...
Iirc if you run your own DNS-server/bind-instance (for DNS lookups, not just responding to internet DNS requests), you have a options file which contains references to forwarders for all the TLDs.
How will managing new TLDs from a server/bind-perspective play out? Will there be a new, hidden ".global" TLD you can forward, or "default" forwarder you can configure to handle this?
Basically I'm not sure how this will play out with my bind-setup and if it will require any action from me as a server-admin, apart from "apt-get update". Anyone here have any inside info?
Your DNS server will simply ask the root servers. Those are listed in a file (root.hint on BIND) and will tell you which server is authoritative for the TLD in question.
I'm not aware of any setups explicitly storing the TLD servers themselves (of course, they'll be in cache.)
For at least one DNS server I've setup (I don't know much about it, to be upfront) all requests for which that server did not have an authoritative response were simply forwarded to an upstream ISP server. Maybe this is an atypical setup, or I'm describing a different problem to the one you're envisaging.
"Make it your upstream provider's problem" isn't a very helpful piece of advice if you're running that provider, I suppose!
Iirc if you run your own DNS-server/bind-instance (for DNS lookups, not just responding to internet DNS requests), you have a options file which contains references to forwarders for all the TLDs.
How will managing new TLDs from a server/bind-perspective play out? Will there be a new, hidden ".global" TLD you can forward, or "default" forwarder you can configure to handle this?
Basically I'm not sure how this will play out with my bind-setup and if it will require any action from me as a server-admin, apart from "apt-get update". Anyone here have any inside info?