On Tue, Mar 15, 2005 at 03:57:20AM +0100, Brad Knowles wrote:
> At 6:23 PM -0800 2005-03-14, Phil Dibowitz wrote:
> 
> > Or - lets say we'd done this with a newer company, or ultradns when they 
> > were
> > new... but then they started doing questionable things... so we pull their
> > delegation. Except that despite _owning_ usc.edu, I can't exert any 
> > control
> > over www.usc.edu once I've delegated it - even to revoke that 
> >delegation. This
> > doesn't follow, at least in my mind.
> 
> 	If you own the parent zone, then you can yank the delegation for 
> the child zone.  Wherever you point that new delegation, they are 
> authoritative for that information.  Whatever information you may 
> have about that zone (beyond the NS records) is just glue and is not 
> authoritative.
> 
> 	Now, if you delegate that zone to yourself, you can be 
> authoritative for both the parent and the child.
> 
> 
> 	Either way, once the delegation is pointed somewhere else, it 
> shouldn't matter what the old server operators do.
Unless the old server still answers for that domain...  which is what happened
in our case.

But as Mark said, it's all theoretical... but I like hearing other people's
opinions - I'm not infallable. =)

-- 
Phil Dibowitz
Systems Architect and Administrator
Enterprise Infrastructure / ISD / USC
UCC 174 - 213-821-5427


-- Attached file included as plaintext by Ecartis --

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFCNlQp7lkZ1Iyv898RAuJpAKDJ8wMXTPxmNnNzY/H+gChuvvUPbACg2rcP
/xmN51L0m3SV2dobVRiR72k=
=oLTO
-----END PGP SIGNATURE-----