How to define differents objects names for same FQDN object ?

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.

How to define differents objects names for same FQDN object ?

L3 Networker

Hello,

I want to define multiple object name for the same FQDN object. The idea is to have relevent object name for different policies.

For example, I define 2 address objects for FQND myserver.mycompany.com : H_srv_oracle and H_srv_ntp.

Then I define 2 security policies : one with H_srv_oracle for oracle traffic, the other with H_srv_ntp for NTP traffic.

The problem is that only one rule works, the other not.

I am pretty sure that this is related to FQDN DNS resolution, because when I look at the FQDN statistic on the PA device using the request system fqdn show command :

myserver.mycompany.com  (Objectname H_srv_oracle):

                   10.120.187.26              3595                        5

myserver.mycompany.com  (Objectname H_srv_ntp):

                    Not resolved

Why the device isn't able to resolve both objects at the same time ? I have tried to refresh FQDN but it doesn't solve the problem ?

This would be very usefull to easily identify policies based on relevent objects name.

Regards,

Laurent

1 REPLY 1

L2 Linker

Object to IP or FQDN mapping is unique. We cannot use two objects for a single IP or FQDN.

  • 1584 Views
  • 1 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!