Do you organize your internal DNS to allow for future expansion?
When you work in the engineering department where everyone uses Linux and Solaris, yet outside of that department the other 99% of the employees use Windows, including the IT department that exclusively trusts in Microsoft, you sort of get the shaft. It can very much be a you-vs-us game that gets played whenever you need something done. Well I don’t expect them to understand the inner workings of the engineering group or to trust us individually, but as a department within the same organization, we’re all batting for the same team!
We just went from one x86 build server to three. And I fully expected the expansion so I asked IT to reserve IP’s for build-x86-01 through build-x86-05. But what happens when I go to set up 3 more and that last IP address in the bunch is taken? I know it really doesn’t matter, and it’s part of the point of having DNS in the first place. Who really cares about IP addresses when you have a name to rely on — this guy! ME!!! I like contiguous addressing for functionally related servers. It just makes it nice and pretty!
So am I the only one out there that likes to set aside blocks? 5 in a row here for ldap replicas, 10 over here for build servers, 101-254 on the next 5 subnets for dhcp addresses… and on and on. In a large organization you wouldn’t have servers mixed in with dhcp addressed workstations would you? So why not try to keep it organized on a small network?!
oh, and a disclaimer – I fudged some of the above to protect the innocent :)