Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 27 subscribers
  • Views 7002 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Using wildcard with complex FQDN hostname

Speatech

Hi,

 

complex FQDN hostnames (ex.: 11.133.226.35.bc.googleusercontent.com) are not resolved by using wildcard (*.bc.googleusercontent.com). 

 

Any workaround?

 



This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    a bit more information would help eg where are you using this wildcard FQDN and what are you trying to achieve?

    Ian

  • 0 in reply to rfcat_vk

    rfcat_vk said:

    Hi,

    a bit more information would help eg where are you using this wildcard FQDN and what are you trying to achieve?

    Ian

     

    Because the destination IP is dynamic.

     

    Details : 

    We need to access Nest cameras recordings on the cloud. When accessing the recording on the web, the Firewall IPS is triggered and that results in a choppy video. The solution is to create a rule :

     

    Destination : Nest cloud server IPs

    IPS : None

     

    I was able to make it work by getting few destination IPs from the log viewer :35.193.198.159,35.232.28.250,35.192.56.207,35.230.168.221.... But these IPs change frequently.

    A reverse lookup return this :

    35.193.198.159  returns 159.198.193.35.bc.googleusercontent.com
    35.232.28.250  returns 250.28.232.35.bc.googleusercontent.com

    ...

     

    Since the IPs are dynamic, I need the DNS to help figure out the new IPs. FQDN is then needed. 

     

     

     

  • 0 in reply to Speatech

    Hi,

    please post a screen shot of your expanded rule.

    Thank you

    Ian

Reply Children
No Data