I think most people are running into the issue, that they think "microservices" are something new and hip and they don't have a clue on how to break down problems a meaningful way.
PS: Another VERY interesting read, and also maybe a bit unrelated to container hosting is "Testing Strategies in a Microservice Architecture": http://martinfowler.com/articles/microservice-testing/. I'd love to hear some more thoughts about that and how services like giantswarm could help with that...
There are a couple solutions that do that - none of them I find sufficient. If you want to clone live traffic, that's probably okay, but recording traffic and replaying it in a usable fashion is a non-trivial task. e.g. systems tend to be dynamic so your recordings would need to be dynamic too in order to be realistic.
this is especially challenging actually. just because you own the domain name, doesn't mean you own the infrastructure you are pointing your DNS records to!
So adding DNS records is pretty useless to provide proof that you own the resources under test.