# DNS: lookup failed for user with dot "."

**URL:** <https://forum.pritunl.com/t/dns-lookup-failed-for-user-with-dot/439>\
**Category:** Pritunl VPN\
**Created:** [October 7, 2022, 4:08am UTC](https://forum.pritunl.com/t/dns-lookup-failed-for-user-with-dot/439 "2022-10-07T04:08:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![iqbalaydrus](https://forum.pritunl.com/user_avatar/forum.pritunl.com/iqbalaydrus/32/163_2.png) [@iqbalaydrus](https://forum.pritunl.com/u/iqbalaydrus)\
**Post date:** [October 7, 2022, 4:08am UTC](https://forum.pritunl.com/t/dns-lookup-failed-for-user-with-dot/439/1 "2022-10-07T04:08:01Z")

</div>

Our pritunl is using google SSO. Some users have dot in their username, for example: “[user.user@example.com](mailto:user.user@example.com)”, and their lookup fails with:

```auto
➜ repos ping user.user.example.vpn
ping: cannot resolve user.user.example.vpn: Unknown host

```

pinging their ips directly works. lookup for other users without dots also works. reverse lookup for the affected users also works.

---

<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:** [October 7, 2022, 5:22am UTC](https://forum.pritunl.com/t/dns-lookup-failed-for-user-with-dot/439/2 "2022-10-07T05:22:02Z")

</div>

This will be fixed in the next release by replacing `.` with `-`

---

<div class="post-metadata">

**Author:** ![iqbalaydrus](https://forum.pritunl.com/user_avatar/forum.pritunl.com/iqbalaydrus/32/163_2.png) [@iqbalaydrus](https://forum.pritunl.com/u/iqbalaydrus)\
**Post date:** [October 7, 2022, 5:38am UTC](https://forum.pritunl.com/t/dns-lookup-failed-for-user-with-dot/439/3 "2022-10-07T05:38:41Z")

</div>

That’s a great news! Thank you
