[Bind10-uides] an interesting possibility for a guiding principal

[Jerry Scharf]

What if we followed an experienced DNS consultant that walked into anew job?

Their first job would be to understand the current DNS configuration and 
contents, then determine what their client was trying to do, possibly 
guiding that discussion to get the right answers out.

They would then take the combination of what they have and what they are 
trying to do, and organize it into a rational structure that has the 
necessary components and the right relationships.

Finally, they would translate this structure into a combination of 
direct data/configurations and tools to create all the right things that 
the nameservers need to offer the right things the right way.


This is very close to what I see as the ideal case for the tool. The 
tool first reads the current state (BIND9 zones and configs) ans/or asks 
a series of questions that guide the basic layout, possibly adding some 
education along the way. It takes this to build an intermediate data 
store in which the logical entities are well organized to the needs of 
the job. Finally it emits the lower level RFC and bind10 data to cause 
the right things to be offered the right way.


If we got N DNS consultants in a room and stroked all their egos 
appropriately, could we find just about all we need to design the 
current and near future needs of the tool?

jerry