# Cant resolve AWS private hosted zone DNS with pritunl enterprise

**URL:** <https://forum.pritunl.com/t/cant-resolve-aws-private-hosted-zone-dns-with-pritunl-enterprise/2612>\
**Category:** Pritunl VPN\
**Tags:** pritunl\
**Created:** [November 14, 2024, 2:39pm UTC](https://forum.pritunl.com/t/cant-resolve-aws-private-hosted-zone-dns-with-pritunl-enterprise/2612 "2024-11-14T14:39:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gk27](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/g/7feea3/32.png) [@gk27](https://forum.pritunl.com/u/gk27)\
**Post date:** [November 14, 2024, 2:39pm UTC](https://forum.pritunl.com/t/cant-resolve-aws-private-hosted-zone-dns-with-pritunl-enterprise/2612/1 "2024-11-14T14:39:14Z")

</div>

Hi team,

I’ve a Pritunl enterprise subscription, i’m trying to access private hosted zone record but unable to do so. I am able to access the private ip, and the private DNS is also being resolved from the private instance, but unable to do so when i’m connected to Pritunl.

In my server settings -

1. I’ve enabled DNS routing and
2. Added 192.168.0.2, 8.8.8.8 as my DNS server (192.168.0.0/16 being my VPC CIDR)
3. Added a NAT route - 192.168.0.2/32

can someone please help what is being missed here? Tried with multiple configuration changes but unable to make it work.

Thanks.

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [November 14, 2024, 11:32pm UTC](https://forum.pritunl.com/t/cant-resolve-aws-private-hosted-zone-dns-with-pritunl-enterprise/2612/2 "2024-11-14T23:32:46Z")

</div>

Only the AWS DNS server should be configured in the server settings, macOS will prioritize `8.8.8.8` even if it is not the first server. The client DNS mapping option should also be enabled to proxy DNS requests through the Pritunl server.

---

<div class="post-metadata">

**Author:** ![gk27](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/g/7feea3/32.png) [@gk27](https://forum.pritunl.com/u/gk27)\
**Post date:** [November 16, 2024, 3:06am UTC](https://forum.pritunl.com/t/cant-resolve-aws-private-hosted-zone-dns-with-pritunl-enterprise/2612/3 "2024-11-16T03:06:01Z")

</div>

I made sure the AWS DNS server in settings, and enabled the DNS mapping option as well along with the NAT route /32. But still not able to do so which is strange. Could you please guide further on how can I resolve this?

---

<div class="post-metadata">

**Author:** ![gk27](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/g/7feea3/32.png) [@gk27](https://forum.pritunl.com/u/gk27)\
**Post date:** [November 16, 2024, 5:10am UTC](https://forum.pritunl.com/t/cant-resolve-aws-private-hosted-zone-dns-with-pritunl-enterprise/2612/4 "2024-11-16T05:10:59Z")

</div>

When I start my Pritunl server, at that time I can’t resolve any DNS on that host.

---

<div class="post-metadata">

**Author:** ![gk27](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/g/7feea3/32.png) [@gk27](https://forum.pritunl.com/u/gk27)\
**Post date:** [November 21, 2024, 5:11am UTC](https://forum.pritunl.com/t/cant-resolve-aws-private-hosted-zone-dns-with-pritunl-enterprise/2612/5 "2024-11-21T05:11:57Z")

</div>

This got resolved after changing the virtual network CIDR of the pritunl server as it was overlapping with my vpc network
