Possible problem with FQDN adresses in security policies

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Possible problem with FQDN adresses in security policies

L4 Transporter

Helo

I have few policies that uses FQDN adresses as a sources. Today one of my friends try to conenct to serwer with putty - but he can't connect.

He used modem with dynamic IP but he used dyndns.org service and I have in policy his domain name.

I also ping this address from my workstation and I got proper IP.

According to What Happens to FQDNs in a Security Policy when DNS Time-to-Live Expires and Device Cannot Reach DNS...

2014-03-24_130423.png

AS we can see IP with 94.42.x.x its his proper IP.

Finally I puted to this policy IP (insted of FQDN) and now its working, bum I'm courious what was happend to me.

Second problem, I'm not CLI guy, but I'm trying... when I try to ping such IP I got:

admin@PA-200> ping host wp.pl

PING wp.pl (212.77.100.101) 56(84) bytes of data.

From 192.168.50.5 icmp_seq=1 Destination Host Unreachable

From 192.168.50.5 icmp_seq=2 Destination Host Unreachable

From 192.168.50.5 icmp_seq=3 Destination Host Unreachable

How to correct my settings? I'm using serveral different settings (diffrerent IP's) in Device>Services>Service route configuration.

Could someone explain that?

With regards

SLawek

0 REPLIES 0
  • 1680 Views
  • 0 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!