DNS name space best practices

[Federico Voges]

Hi,

I'm having a hard time trying to convince some people at work, that
cramming organization (company), environment (dev, QA, prod), data
center (we have multiple data centers and also use Amazon cloud) and
the actual host name into the short host name, and using flat DNS name
space ( XX...XXX.company.com) is a bad idea. I'm proposing to use
something more sensible like appnameNNN.env.dc.ogranization.com (we
have multiple domains due to multiple acquisitions). To make it worst,
they are using the same "field" to specify environment and data
center.

I've been trying to find examples (like white papers, best practices
docs, etc) to support my proposal but the closest thing I've found is
for Windows AD. The rest of the best practices docs only talk about
deploying BIND and not how to design your DNS zones.

Does anyone have any link that my help having to implement this insane
flat name space nightmare?

Thanks,
Federico.