# Question about required DNS configuration for collabora with nextcloud integration? **URL:** \ **Category:** Installation & Configuration\ **Created:** [July 7, 2022, 3:13pm UTC](https://forum.collaboraonline.com/t/question-about-required-dns-configuration-for-collabora-with-nextcloud-integration/1233 "2022-07-07T15:13:00Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![wwe](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/wwe/32/534_2.png) [@wwe](https://forum.collaboraonline.com/u/wwe)\ **Post date:** [July 27, 2022, 8:28am UTC](https://forum.collaboraonline.com/t/question-about-required-dns-configuration-for-collabora-with-nextcloud-integration/1233/2 "2022-07-27T08:28:08Z")
You should have both Nextcloud and Collabora having valid DNS names (which is prerequisite for TLS). All this names should exists in DNS and be resolvable by each component - client Nextcloud server and Collabora **must** resolve all the DNS names to the right ip (your real server ip in this case as 127.0.0.1 might be not the right one especially if you use some virtualization) You can refer to Nextcloud forum where I posted some drawings and references: > **[Yet another problem with Nextcloud Office/Collabora](https://help.nextcloud.com/t/yet-another-problem-with-nextcloud-office-collabora/134179/11?u=wwe)** > > I agree, given the fact item within “srv” are containers sharing the same docker network expose is good choice. In this sample you only need to include ports on reverse proxy and hide both applications within docker. --- _[View the full topic](https://forum.collaboraonline.com/t/question-about-required-dns-configuration-for-collabora-with-nextcloud-integration/1233)._