Thank you for a very speedy reply, Melih. :-TU
How can I troubleshoot why it does not work for me?
Yeah listen to Melih. DNS is DNS it should not be OS specific. It’s main purpose is to resolve friendly names (www.google.com) for example to IP addresses to route you to the correct place. Comodo is doing something unique and makeing the DNS service more secure and giving you more control over the content you want to filter. LONG LIVE COMODO!
hmm…i will ask our guys to check it out
Thank you, Melih. It’s odd I have no problem using the old Comodo DNS, OpenDNS, or Level3 DNS.
This is all I get when pinging the new server.
[attachment deleted by admin]
ICMP (ping) might not be always on for various reasons. Could you possibly run a traceroute for us? In Windows, what is traceroute and how do I use it?
Hi Brian.
[attachment deleted by admin]
Update. The beta IPs are now working for me. I notice a different route through Miami in Tracert.
[attachment deleted by admin]
Yes we found an issue with a peering partner, the issue was resolved yesterday afternoon. The reason you see two different routes is because we use an anycast network to serve the DNS requests. This allows us to have multiple servers be geographically distributed and with the most possible uptime and response speed.
Any update on it?
Still in BETA? 
Thanks for fixing, and thanks for the explanation. :-TU
I work with a program over 4 public computer labs serving about 100 pcs total. We are currently in the process of evaluating new/additional filtering services to our networks as our currently solution is become very poor in regards to filtering. I’d love to take this dns service for a spin in the beta test within one of my labs to see how it works out.
I created the a user account; Budda - royceb@live.com
Each time I try to add a network I’ve got the “Ouch” blank page 88) 
[attachment deleted by admin]
Right now, NortonDNS is blocking www.google.com … I can’t believe (it’s on security or ■■■■■■■■■■■ categories). Really, I can’t believe on Symantec…
Is Comodo Secure DNS still being developed? ???
yes
Thanks Melih. I’ll try again to register the network.
This may have already been mentioned. I would like to see a button or link on the Warning: Unsafe Website Blocked! page that comes up when you try to visit a blocked site, that will let you continue on to the blocked site. Of course, there should be a warning that you are proceeding at your own risk (or something to that effect).
So will
156.154.70.22 156.154.71.22 < The Current V1 Comodo DNS be Shut down when V2 Secure Comodo DNS is fully running! As in no more Beta Stage and is fully out ?
I’m just wondering that is all.
Nige
Hi All Again.
I downloaded the New CIS 5.8 and I say it is great. The Reason why I bring this up under the DNS Part of the Forum is when I installed CIS 5.8 I got my DNS Setting changed for me.
However, what I have noticed is in the First box under Preferred DNS server: it shows 8.26.56.26 < That is the Secure DNS Code. However, on the Alternate DNS server: it shows 156.154.71.22 < and that code is from DNS Version 1.
So My Question is should I leave this settings in Place while Secure DNS is still in beta? Alternatively, should I change the Alternate DNS server: 8.20.247.20 or just leave it as 156.154.71.22 for now.
Regards
Nige
It’s up to you if you want to use the beta service. They’ve previously pushed it with the Comodo Dragon downloads, and if they’re now pushing it with the latest CIS, they obviously feel it’s ready for a wider audience.
The only drawback to using the beta service is that unless you register for an account and set your filtering options, you may be getting site filtering that you don’t want. (Above and beyond simple malware site blocking)
I would definitely leave the alternate address as it is. This way if the beta service goes down for some reason, you still have the old DNS service to fall back on, so you’ll still have net connectivity.