Webex domain showing SERVFAIL Cloudflare DNS services

I couldn’t connect to webex this morning. Looked into it and dig is giving a SERVFAIL status on both DNS servers. I can dig on other DNS and such and it works. Both Cloudflare DNS are otherwise seeming to work just fine. It’s just webex I can’t query that I’ve noticed.

Here’s some dig info (sorry for not including it at first):

[email protected]:~ $ dig @1.1.1.1 webex.com

; <<>> DiG 9.11.5-P4-5.1+deb10u7-Raspbian <<>> @1.1.1.1 webex.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 11475
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; OPT=15: 00 16 61 74 20 64 65 6c 65 67 61 74 69 6f 6e 20 77 65 62 65 78 2e 63 6f 6d 2e ("..at delegation webex.com.")
;; QUESTION SECTION:
;webex.com.                     IN      A

;; Query time: 25 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Sep 19 10:20:14 EDT 2022
;; MSG SIZE  rcvd: 68
[email protected]:~ $ dig @8.8.8.8 webex.com

; <<>> DiG 9.11.5-P4-5.1+deb10u7-Raspbian <<>> @8.8.8.8 webex.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20354
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;webex.com.                     IN      A

;; ANSWER SECTION:
webex.com.              81      IN      A       64.68.121.205

;; Query time: 15 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Sep 19 10:22:10 EDT 2022
;; MSG SIZE  rcvd: 54

[email protected]:~ $ dig @1.1.1.1 +short CHAOS TXT id.server
"BOS"

Nothing on this? Webex still can’t be queried from 1.1.1.1 or 1.0.0.1. I’ve tried from multiple ISPs.

I’d really like to stop using Google for DNS.

Seeing the same error with BOS

dig +short CHAOS TXT id.server @1.1.1.1
“BOS”

Same issue here only affecting the Webex domain and I’m hitting the BOS resolvers. I’ve tried on 1.1.1.1 and .2 with the same servfail. Google resolvers work fine for me.

Dig result

$ dig webex_dot_com @1.1.1.1

; <<>> DiG 9.16.1-Ubuntu <<>> webex_dot_com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 5592
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; OPT=15: 00 16 61 74 20 64 65 6c 65 67 61 74 69 6f 6e 20 77 65 62 65 78 2e 63 6f 6d 2e (“…at delegation webex_dot_com.”)
;; QUESTION SECTION:
;webex_dot_com. IN A

;; Query time: 20 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Sep 20 08:02:07 EDT 2022
;; MSG SIZE rcvd: 68

I am having similar issue unable to resolve webex recently

[email protected]:~ $ dig webex.com @1.1.1.1

; <<>> DiG 9.11.5-P4-5.1+deb10u7-Raspbian <<>> webex.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 2586
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; OPT=15: 00 16 61 74 20 64 65 6c 65 67 61 74 69 6f 6e 20 77 65 62 65 78 2e 63 6f 6d 2e ("..at delegation webex.com.")
;; QUESTION SECTION:
;webex.com.			IN	A

;; Query time: 2 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Sep 20 16:06:01 CDT 2022
;; MSG SIZE  rcvd: 68

[email protected]:~ $ dig webex.com @1.0.0.1

; <<>> DiG 9.11.5-P4-5.1+deb10u7-Raspbian <<>> webex.com @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 613
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; OPT=15: 00 16 61 74 20 64 65 6c 65 67 61 74 69 6f 6e 20 77 65 62 65 78 2e 63 6f 6d 2e ("..at delegation webex.com.")
;; QUESTION SECTION:
;webex.com.			IN	A

;; Query time: 3 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Tue Sep 20 16:06:29 CDT 2022
;; MSG SIZE  rcvd: 68

[email protected]:~ $ dig webex.com @8.8.8.8

; <<>> DiG 9.11.5-P4-5.1+deb10u7-Raspbian <<>> webex.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43890
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;webex.com.			IN	A

;; ANSWER SECTION:
webex.com.		45	IN	A	64.68.121.205

;; Query time: 12 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Sep 20 16:06:42 CDT 2022
;; MSG SIZE  rcvd: 54

[email protected]:~ $ dig +short CHAOS TXT id.server @1.1.1.1
"MCI"
[email protected]:~ $ dig +short CHAOS TXT id.server @1.0.0.1
"MCI"

Also having issues getting webex.com to resolve this morning.

[email protected]:~$ dig webex.com @1.1.1.1

; <<>> DiG 9.18.1-1ubuntu1.1-Ubuntu <<>> webex.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 29706
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 22 (No Reachable Authority): (at delegation webex.com.)
;; QUESTION SECTION:
;webex.com.			IN	A

;; Query time: 28 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Wed Sep 21 08:48:31 EDT 2022
;; MSG SIZE  rcvd: 68

jom[email protected]:~$ dig webex.com @1.0.0.1

; <<>> DiG 9.18.1-1ubuntu1.1-Ubuntu <<>> webex.com @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 55309
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 22 (No Reachable Authority): (at delegation webex.com.)
;; QUESTION SECTION:
;webex.com.			IN	A

;; Query time: 24 msec
;; SERVER: 1.0.0.1#53(1.0.0.1) (UDP)
;; WHEN: Wed Sep 21 08:48:38 EDT 2022
;; MSG SIZE  rcvd: 68

[email protected]:~$ dig webex.com @8.8.8.8

; <<>> DiG 9.18.1-1ubuntu1.1-Ubuntu <<>> webex.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30761
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;webex.com.			IN	A

;; ANSWER SECTION:
webex.com.		221	IN	A	64.68.121.205

;; Query time: 32 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Wed Sep 21 08:48:49 EDT 2022
;; MSG SIZE  rcvd: 54

[email protected]:~$ dig +short CHAOS TXT id.server @1.1.1.1
"BOS"
[email protected]:~$ dig +short CHAOS TXT id.server @1.0.0.1
"BOS"

Public IP can be shared privately with Cloudflare staff if helpful.

Hm. No problems here:

(server in Germany)

# dig @1.1.1.1 webex.com

; <<>> DiG 9.18.1-1ubuntu1.2-Ubuntu <<>> @1.1.1.1 webex.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12882
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;webex.com.			IN	A

;; ANSWER SECTION:
webex.com.		300	IN	A	64.68.121.205

;; Query time: 23 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Thu Sep 22 10:42:44 WEST 2022
;; MSG SIZE  rcvd: 54

Nor here (home, in Portugal):

$ dig @1.1.1.1 webex.com

; <<>> DiG 9.10.6 <<>> @1.1.1.1 webex.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15674
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;webex.com.                     IN      A

;; ANSWER SECTION:
webex.com.              141     IN      A       64.68.121.205

;; Query time: 78 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Sep 22 10:44:06 WEST 2022
;; MSG SIZE  rcvd: 54

No problem here, either (Bluehost server, somewhere in Provo, Utah, USA):

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.62.rc1.el6_9.4 <<>> @1.1.1.1 webex.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3589
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;webex.com.			IN	A

;; ANSWER SECTION:
webex.com.		197	IN	A	64.68.121.205

;; Query time: 2 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Sep 22 03:48:43 2022
;; MSG SIZE  rcvd: 43

DigWebInterface also doesn’t show any issues with webex.com. At least not at the time of writing this!

As of today, this issues seems to have resolved for BOS at least.

1 Like

Unfortunately another user with the same issue since yesterday 2022-09-26…

$ nslookup webex.com 1.1.1.1
Server:         1.1.1.1
Address:        1.1.1.1#53

** server can't find webex.com: SERVFAIL

I’m located in Germany and my homeserver seems to be in Munich:

$ dig +short CHAOS TXT id.server @1.1.1.1
"MUC"

Obviously there is no general problem that has Cloudflare DNS with webex.com, tested it also with Dig web interface.

So is there anything I can do except waiting? Unfortunately WebEx is the central communication platform in our company and with this issue I’m locked out in my homeoffice if I’d stay with 1.1.1.1.

Is someone from Cloudflare staff reading along?

Thanks and have a nice day!

Maybe this helps, too:

$ dig webex.com @1.1.1.1

; <<>> DiG 9.16.33-Debian <<>> webex.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4071
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 22 (No Reachable Authority): (at delegation webex.com.)
;; QUESTION SECTION:
;webex.com.                     IN      A

;; Query time: 43 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Sep 27 21:28:59 CEST 2022
;; MSG SIZE  rcvd: 68

In THIS post the staff member @anb explained the reason behind “No Reachable Authority” and contacted the responsible operator. It would be great if someone from Cloudflare Team could pick up the ball! :wink:

We’ve applied a workaround here and reached out to the operator to remedy the actual issue. Thanks for reporting.

Works like a charm! :smile:
Thank you for immediately solving this issue! :+1:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.