Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Explorer

status.webex.com not working

Hello Everyone.

I have a query as currently our firewall Cluster is not allowing https://status.webex.com.

In order to fix this I have created a domain FQDN object as .status.webex.com and used this in the Access policy. However its not working. 

Any help on this will be very helpful?

[Expert@R80.40:0]# nslookup
> status.webex.com
Server: 10.40.14.2
Address: 10.40.14.2#53

Non-authoritative answer:
status.webex.com canonical name = divjhjhd2ifiw.cloudfront.net.
Name: divjhjhd2ifiw.cloudfront.net
Address: 143.204.198.128
Name: divjhjhd2ifiw.cloudfront.net
Address: 143.204.198.52
Name: divjhjhd2ifiw.cloudfront.net
Address: 143.204.198.111
Name: divjhjhd2ifiw.cloudfront.net
Address: 143.204.198.43
>

0 Kudos
5 Replies
Highlighted
Employee
Employee

Hi Rano,

I can't seem to replicate this issue

Any chance you have the relevant log to to share, so that we can figure out what's blocking this site for you?

Thanks,

Maya

0 Kudos
Highlighted
Explorer

Hello Maya,

Thanks for your reply.

I have asked customer to generate some traffic so I can check the logs may be a remote session with customer will be the next step as in this case I dont know the Destiination IP so the best option will be to track it down with Source IP.

Let me know if you have any more thought on this.

Thanks

0 Kudos
Highlighted
Employee
Employee

Have you tried the updatable object for Webex?

0 Kudos
Highlighted
Explorer

Hi AlejandroH,

Thanks for the reply. Currently in the rule we are already using Webex updatable object and its allowing the Webex traffic apart from above two URLs.

Let me know if you have any more thoughts on this?

Thanks

0 Kudos
Highlighted
Admin
Admin

Recommend a TAC case here.

0 Kudos