https://community.checkpoint.com/t5/Firewall-and-Security-Management/Domain-Object/m-p/234011#M45328 <P>I have created a test rule to allow one server to access <A title="Benteng Putri Hijau" href="http://jurnalsumut.id" target="_self">jurnalsumut</A>.id, by creating a domain object using .jurnalsumut.id.</P><P>However, I think the domain object is not working properly, because the server still cannot access jurnalsumut.id. Checking and unchecking the FQDN in the domain object does not give the expected result.</P> Thu, 28 Nov 2024 06:20:12 GMT Jurnalsumut 2024-11-28T06:20:12Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Domain-Object/m-p/234011#M45328 <P>I have created a test rule to allow one server to access <A title="Benteng Putri Hijau" href="http://jurnalsumut.id" target="_self">jurnalsumut</A>.id, by creating a domain object using .jurnalsumut.id.</P><P>However, I think the domain object is not working properly, because the server still cannot access jurnalsumut.id. Checking and unchecking the FQDN in the domain object does not give the expected result.</P> Thu, 28 Nov 2024 06:20:12 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Domain-Object/m-p/234011#M45328 Jurnalsumut 2024-11-28T06:20:12Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Domain-Object/m-p/234013#M45330 <P>What version/JHF?<BR />Are your clients and gateway using the same DNS servers?<BR />If not, are you 100% certain that both DNS servers resolve to the same IPs?</P> <P>Note that non-FQDN objects rely on Reverse DNS (IP to name) to work properly, which it won't in most cases.<BR />See also:&nbsp;<A href="https://support.checkpoint.com/results/sk/sk161612" target="_blank">https://support.checkpoint.com/results/sk/sk161612</A>&nbsp;</P> Thu, 28 Nov 2024 06:52:28 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Domain-Object/m-p/234013#M45330 PhoneBoy 2024-11-28T06:52:28Z