BIND9 maximal zone file

[Li Bin, SLC COM CD/MN R&D SE (BJ)]

Thanks, it is not standardization so far, but is a proposal way to solve the MNP(Mobile Nubmer Portability) issue, if every subscriber in one registry owned a separate zone file, it should easy realize number portability. Certainly there are any other soultion for the MNP topic.


B.R.
LiBin

-----Original Message-----
From: Stephane Bortzmeyer [mailto:bortzmeyer at nic.fr] 
Sent: 2005年11月23日 14:24
To: Li Bin, SLC COM CD/MN R&D SE (BJ)
Cc: bind-users at isc.org
Subject: Re: BIND9 maximal zone file

On Wed, Nov 23, 2005 at 08:38:16PM +0800,
 Li Bin, SLC COM CD/MN R&D SE (BJ) <bin_li at siemens.com> wrote 
 a message of 27 lines which said:

> becuase according ENUM schema, it should have a separete zone for
> every E.164 number

I'm not an ENUM expert but I wonder where you've found that strange
rule. There is a *domain* for each E164 number but a *zone* per
number, no, I find it hard to believe.

> assume BIND support more than those 1 million zone files,

Whatever the response here (except if it comes from Mark Andrews :-)
do not blindly accept it: test. Write a program which generates a
named.conf with one million zones and see what happens. This is sound
engineering practice, by the way and not BIND-specific: do not blindly
trust theoretical analysis, test.