The Domain Access module for Drupal is for sorting and displaying content and themes/styles depending on the added system aware domains, which have to be covered, and only works with proper virtual host settings on server for incoming calls. It can achieve to give the visitor the feeling to be on two different places or at near but slidely different places. It is made for the cases where you definitely need a shared backend and content or design pool for two different domains but should not be considered for any case. It isn't as easy as it reads on the module project page. It needs further understanding how paths work in Drupal universe and can get broken on bigger updates. And you will have a hard time to teach a views view to be filtered different depending on incoming domain, even with Domain Views Module at hand.
I sadly can not confirm to use the other recommendation Admin Views modules because it is too limited in its approach and its not true that views doesn't support overriding admin pages. It works very well and is mostly one of my first steps in a new Drupal installation. It even works great with the different tabs on the admin pages (like admin/content with the files or comments tab) and there are enough tutorials around explaining the path settings to setup and how it works. I hope I make noone upset here, but I think it is not true to say, that you need Admin View module for overriding admin pages like admin/content etc. Maybe there was a time when it was hard to achieve this with views allone, but in the meantime views has a lot of options to make it work and even with more options than Admin Views module provides out of the box and stucks there on its limits.