> -----Original Message-----
> From: Jeff Chan [mailto:[EMAIL PROTECTED]
> Sent: Saturday, January 26, 2008 12:23 PM
>
> Quoting Jeff Chan <[EMAIL PROTECTED]>:
>
> > Quoting Giampaolo Tomassoni <[EMAIL PROTECTED]>:
> >
> >> The TLD root servers delegate the control of the II level domain to
> the NS
> >> servers defined at registration time. That is delegation. But from
> there,
> >> warping the entire domain to different NSes is not delegation.
> >
> > It is delegation.
NSes authoritative for a domain delegating that whole domain to some other
NSes is "delegation"?
I would rather name it "abdication". "Zone warping" likes me more, however.
> And more specifically not all delegations of this type are
> illegitimate. Sometimes there are legitimate reasons why someone
> might want or need to delegate DNS authority for a given domain to
> another nameserver.
Agreed already. See <[EMAIL PROTECTED]@libero.it>:
> Then, of course there is people ... even that are somehow mandated
> to warp their zone, but I don't see big numbers here.
> Therefore using it as a spam test will probably result in false
> positives.
Agreed already. See <[EMAIL PROTECTED]@libero.it>:
> After all, every SA rule has its own FPs, isn't it?
> This type of delegation is very easy to do. Normally if one registers
> a domain using dns1.foo.com and dns2.foo.com, the NS records would
> look like:
>
> mydomain.com IN NS dns1.foo.com.
> mydomain.com IN NS dns2.foo.com.
>
> In order to delegate them elsewhere, the NS record for the domain is
> changed:
>
> mydomain.com IN NS dns1.bar.com.
> mydomain.com IN NS dns2.bar.com.
It is easy to do, but there is no need to unless you want to play ping-pong
with responsibilities when somebody files a claim statement against your
org...
Giampaolo
> Jeff C.
