geographic load-balancing and organizationally external secondaries

[Neil Harkins]

Hi. There are several solutions for geographic load-balancing in DNS, 
but all seem to require administrative ownership/non-standard
configuration of all the nameservers involved, which defeats the 
purpose of having external entities providing slave secondary service. 

However, if there were a way to prioritize/weight NS records, 
both requirements could be met easily. i.e. Geo-load-balancing
from servers you control, then fall back to external slaves
which have non-balanced static responses.

Two not-necessarily realistic solutions come to mind: 

A) An extension to the DNS spec to allow weights 
   on NS records similar to those on MX records. 
   Unlikely. 

B) A hack to the remote nameservers allowing 
   a delay to be configured per zone.
   Since the DNS caches close to the end user
   will most likely be using RTT to determine
   which NS to query, they should prefer the
   primaries (without the delay configured).
   This is obviously less valid, as it requires
   the modification happen at the external site,
   not to mention that it negatively impacts
   their performance.

Any other ideas on how to accomplish this?
Has there been any other initiatives  
concerning weighting NS records?

I apologize if this is not the appropriate forum, 
but a lot of the relevant players are here,
thus hopefully can/will gauge validity.

Thanks,
-neil harkins