So I'm in the middle of building a solution for a customer, one that we will be managing moving forward.
To give you an idea of the size, talking around 350Ghz of processor and 500GB of memory over 16 hosts. All hooked up to a group of EQL iSCSI SANS.
Now the question of DNS has come up. Of course most organisations run some sort of AD and so have their own internal DNS infrastructure in house. We dont.
Our own vmware setups that we use in-house for dev and production environments have simply been setup by managing hosts files, that is, all DNS is held within the hosts/virtualcentres and that allows everything to connect together and work just fine.
However with this customer setup there are some other issues, for example there is going to be at least another environment in another DC and so the number of hosts is going to double and basically it's probably going to end up being a pain to manage just updating hosts files.
So what do we do? I don't really want to setup DNS servers and start managing it like that.
What about public dns records? I'm sure there are all sorts of reasons why that is a bad idea but this infrastructure is being designed to host a web application so external connectivity isn't one of em.
Is security even an issue? So what if vmhost-1.whatever.com is public and resoves to 10.10.10.4... it's still not routable though we'de rather it was a secret in the first place.
What does everyone think?
