hello David I did what you recommended, but I had to add one more subscription, see the attached graphic, but for the time being all right, it will be tomorrow to prove that the users work.

David Redekop wrote:

Hi Jose, thanks for pointing this out. We do have pre-build Rule Sets (policies) including these two:

Block the Bad - this Rule Set only blocks domains in known blacklists and your ClearOS updates would work on this Rule Set.
Allow only the Good - this Rule Set only allows explicitly specified domains to resolve, and it has a number of them enabled by default, and you can add more

If you're in Whitelist mode, you can use the Subscription section and enable the ClearOS subscription (attachment 1 below)
Then, just make sure you turn it on in your "Allow only the good" Rule Set and you'll be all set (attachment 2 below)

Hope that helps

Essentially you have placed your own server on a whitelist without it having access to ClearOS resources. If you go to your dashboard -> Subscriptions and subscribe to ClearOS and then enable it on your "Allow only the good", you'll be good to go

With kind regards,
David Redekop

Hi Jose, I'm happy to help out here. In your case, you simply have ClearOS itself on a strict whitelist so it's only able to reach out to destinations on your "Allow only the good" ruleset.

We have "subscriptions" as an option. From your dashboard, choose Subscriptions which lists ClearOS as an available subscription. Once you've subscribed to a new Rule/List, just enable it on your "Allow only the good" Rule Set and your updates will be function

With kind regards,
David Redekop

Hi Jose, thanks for pointing this out. We do have pre-build Rule Sets (policies) including these two:

Block the Bad - this Rule Set only blocks domains in known blacklists and your ClearOS updates would work on this Rule Set.
Allow only the Good - this Rule Set only allows explicitly specified domains to resolve, and it has a number of them enabled by default, and you can add more

If you're in Whitelist mode, you can use the Subscription section and enable the ClearOS subscription (attachment 1 below)
Then, just make sure you turn it on in your "Allow only the good" Rule Set and you'll be all set (attachment 2 below)

Hope that helps

I am confused. Gateway Management uses the dnsthingy engine but they appear to be two different products. I'll have to ask the devs what the difference is. I think for dnsthingy support you may be able to e-mail support@dnsthingy.com.

I not use gateway management , I use Dnsthingy , I do not understand why it blocks internet access to the server, PING google.com (10.0.0.2) 56(84) bytes of data.
64 bytes from gateway.liceonuevo.local (10.0.0.2): icmp_seq=1 ttl=64 time=0.019 ms
64 bytes from gateway.liceonuevo.local (10.0.0.2): icmp_seq=2 ttl=64 time=0.047 ms
64 bytes from gateway.liceonuevo.local (10.0.0.2): icmp_seq=3 ttl=64 time=0.053 ms
64 bytes from gateway.liceonuevo.local (10.0.0.2): icmp_seq=4 ttl=64 time=0.047 ms

yum update
Complementos cargados:clearcenter-marketplace, fastestmirror
ClearCenter Marketplace: fetching repositories...
ClearCenter Marketplace: [Errno 110] Expiró el tiempo de conexión


When I deactivate the DNS, the server returns to normal

I have reinstalled the dnsthingy and with the same result

rpm -q dnsthingy
dnsthingy-2.2-18.v7.x86_64

Hmm. I've tried a test. ClearOS 7.5 community running Gateway Management Community behind ClearOS 7.5 Business running Gateway Management Business and I then did a yum update on the community box and it worked fine, as does the Marketplace on the Community box.

On both boxes:

rpm -q dnsthingy

dnsthingy-2.2-18.v7.x86_64

On the Community box:

rpm -qa | grep gateway

app-gateway-management-2.0.9-1.v7.noarch

app-gateway-management-core-2.0.9-1.v7.noarch

app-gateway-management-community-2.0.2-1.v7.noarch

app-gateway-management-community-core-2.0.2-1.v7.noarch

and on the Business box:

rpm -qa | grep gateway

app-gateway-management-business-core-2.0.2-1.v7.noarch

app-gateway-management-2.0.9-1.v7.noarch

app-gateway-management-core-2.0.9-1.v7.noarch

app-gateway-management-business-2.0.2-1.v7.noarch

I am not sure where you are getting a v.1.4.3 from.

Also I believe Gateway Management leverages OpenDNS. Are you able to access their DNS servers OK?