Comodos Secure dns offline ?

Hi there I just ran a check on my system and it shows me that the secondary dns server is offline.

X Connectivity to DNS Server 2 (156.154.70.22) < as you see it shows me X before Connectivity to DNS Server 2 (156.154.70.22)

So if it is offline do I leave it and run on the main Comodo dns server which is running fine.

Regards Nigel

I changed to my DNS server 2 to (8.20.247.20) and ran a test and its running well now. I have not retried the old settings so I’m happy up to now

Regards

Nigel

Yeah, I noticed too the change of the secundary DNS.
Comodo should notify about this important changes, specially to CIS users.
Maybe through “Comodo Message Center” in CIS or something like this.

Old and Beta seem to be working…

$ dig @156.154.70.22 forums.comodo.com

; <<>> DiG 9.9.0 <<>> @156.154.70.22 forums.comodo.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50100
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;forums.comodo.com.             IN      A

;; ANSWER SECTION:
forums.comodo.com.      846     IN      A       91.199.212.149

;; AUTHORITY SECTION:
comodo.com.             1127    IN      NS      ns0.comododns.net.
comodo.com.             1127    IN      NS      ns1.comododns.com.
comodo.com.             1127    IN      NS      ns1.comododns.net.
comodo.com.             1127    IN      NS      ns0.comododns.com.

;; Query time: 197 msec
;; SERVER: 156.154.70.22#53(156.154.70.22)
;; WHEN: Thu May 10 16:44:21 2012
;; MSG SIZE  rcvd: 157


GCB@Enterprise ~
$ dig @156.154.71.22 forums.comodo.com

; <<>> DiG 9.9.0 <<>> @156.154.71.22 forums.comodo.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63720
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;forums.comodo.com.             IN      A

;; ANSWER SECTION:
forums.comodo.com.      176     IN      A       91.199.212.149

;; AUTHORITY SECTION:
comodo.com.             1154    IN      NS      ns1.comododns.com.
comodo.com.             1154    IN      NS      ns0.comododns.net.
comodo.com.             1154    IN      NS      ns1.comododns.net.
comodo.com.             1154    IN      NS      ns0.comododns.com.

;; Query time: 188 msec
;; SERVER: 156.154.71.22#53(156.154.71.22)
;; WHEN: Thu May 10 16:46:38 2012
;; MSG SIZE  rcvd: 157


GCB@Enterprise ~
$ dig @8.26.56.26 forums.comodo.com

; <<>> DiG 9.9.0 <<>> @8.26.56.26 forums.comodo.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12049
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;forums.comodo.com.             IN      A

;; ANSWER SECTION:
forums.comodo.com.      731     IN      A       91.199.212.149

;; AUTHORITY SECTION:
comodo.com.             250     IN      NS      ns1.comododns.com.
comodo.com.             250     IN      NS      ns0.comododns.com.
comodo.com.             250     IN      NS      ns1.comododns.net.
comodo.com.             250     IN      NS      ns0.comododns.net.

;; Query time: 180 msec
;; SERVER: 8.26.56.26#53(8.26.56.26)
;; WHEN: Thu May 10 16:47:01 2012
;; MSG SIZE  rcvd: 157


GCB@Enterprise ~
$ dig @8.20.247.20 forums.comodo.com

; <<>> DiG 9.9.0 <<>> @8.20.247.20 forums.comodo.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60774
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;forums.comodo.com.             IN      A

;; ANSWER SECTION:
forums.comodo.com.      686     IN      A       91.199.212.149

;; AUTHORITY SECTION:
comodo.com.             204     IN      NS      ns1.comododns.com.
comodo.com.             204     IN      NS      ns0.comododns.com.
comodo.com.             204     IN      NS      ns1.comododns.net.
comodo.com.             204     IN      NS      ns0.comododns.net.

;; Query time: 195 msec
;; SERVER: 8.20.247.20#53(8.20.247.20)
;; WHEN: Thu May 10 16:47:47 2012
;; MSG SIZE  rcvd: 157


Thanks for the input Radaghast By your test it does show you that 156.154.70.22 is working for you. I have no issue with it since I have the 2 beta dns servers set-up under my router via command prompt.

Mind you I have not tested the old dns 156.154.70.22 since yesterday. But I will do a new test.

But as I see via your code you ran it thru the forum since it shows its url in the code.

I ran a test under Command Prompt of DNS 8.20.247.20 and I ran a test in DNS 156.154.70.22. So I coped what I found.

But the Interesting thing I noticed the Traceroute got all the way around and it ended back for DNS 8.20.247.20.

But for DNS 156.154.70.22 it started of OK then went ? before it ended back to 156.154.70.22.

So I thought I share the info I found

Regards

Nigel

[attachment deleted by admin]

All CIS Firewall related products should check and update DNS servers if necessary.

But that’s not, what I’m here for.

COMODO new DNS servers are currently dead for me. I’m having serious connectivity issues thanks to those new DNSs for 2 days now. Today is the worst case. No internet connection at all.

[b]https://www.comodo.com/secure-dns/[/b]
Read the first section of text and then move your eyes to the right, do you notice something being off?

More Reliable - Comodo Secure DNS’s server infrastructure currently spans 15 locations (nodes) and five continents around the world. This allows Comodo to offer you the most reliable fully redundant DNS service anywhere. Each node has multiple servers and is connected by several Tier 1 carriers to the Internet.

Maybe it’s time to upgrade your ancient connections and ancient hardware? And that webpage too…

Lucky for you, thanks to Windows’s Advanced settings, users can have more than 2 DNS servers, so maybe opening up few more servers could prevent this server overload issue from happening?

If you’re having a problem with both of the recommended DNS servers:

8.26.56.26
156.154.70.22

You may have a problem elsewhere.

The 8.26.56.0/24 block is allocated to dns.com (Comodo) but the 156.154.70.0/24 is allocated to Neustar (Ultra DNS) from which Comodo lease their earlier servers.