> Source: [sk167933](https://support.checkpoint.com/results/sk/sk167933)

# sk167933 - Resolving name request using SecuRemote DNS not reaching the Security Gateway

| Property | Value |
|----------|-------|
| Solution ID | sk167933 |
| Date Created | 2020-07-20 |
| Last Modified | 2020-07-23 |
| Technical Level | Advanced |
| Products | Endpoint Security |
| Versions | Cloud, E89.X, E88.X |
| OS | Windows |

## Symptoms

- * Resolving name request using SecuRemote DNS is not reaching the Security Gateway.
* Cannot resolve FQDN in internal LAN behind the gateway.
* While using Wireshark on the client (on both virtual adapter and physical adapter), on the virtual adapter the user can see the DNS requests sent. However, he does not see it sent encrypted on the physical adapter. He only sees tunnel test packets.

## Cause

In SmartConsole, in the SecueRemote DNS server's object (under "Domains" \> "Domain patterns") "match only \*.suffix" was selected.  

\* This option accepts only 1 label.  

**Example:**   
When configuring "test.com" as the server object (with this option checked) will match only 1 label which is ".com"

<br />

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content