This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
ABOUT CHECKMATES CYBER SECURITY COMMUNITY & FAQ
Create a Post
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Are you a member of CheckMates?

×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
NhatKha
Contributor
‎2024-08-29 05:14 AM

.

 
0 Kudos
3 Replies
AkosBakos
Advisor
Advisor
‎2024-08-29 05:44 AM

Hi @NhatKha 

What are the configured DNS servers for your cluster?

IP: 10.17.173.5

Akos

----------------
\m/_(>_<)_\m/
the_rock
Legend
Legend
‎2024-08-29 06:46 AM

Thats what came to my mind as well...dns, can you confirm?

Andy

0 Kudos
PhoneBoy
Admin
Admin
‎2024-08-29 12:12 PM

For FQDN objects (which you're clearly using), the gateway periodically queries the configured DNS resolver to find its IP for proper enforcement in the Access Policy.
The Occam's Razor answer is, therefore, at least in your DNS resolver (if not globally), bierbuducunpderdr[.]ddns[.]net resolved to that IP. 
Once that FQDN stopped resolving (it currently doesn't for me), the problem resolved.

How bierbuducunpderdr[.]ddns[.]net resolved to that IP would be a question for the folks who run DDNS (No-IP).

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

View All ≫
Upcoming Events

    Sort by:
    CheckMates Events