Clearly, I had to explain very badly, to create so much confusion.
Confusion can be on my side only, don't worry
The problem only occurs in Zentyal 3.0, I have another proxy with Zentyal 2.2 and does not occur.
This is because in Zentyal 3.0 Proxy module depends on the Users and Groups, and this in turn the DNS, which has not happened in Zentyal 2.2
Not a matter of confusion or understand, this statement is "wrong".
Proxy design is not very different between 2.2 and 3.0 and definitely does not depend on users & groups. Obviously, without users, you can't authenticate but still you can have either transparent or explicit proxy with filtering (users are only needed for profiling)
The problem is that in Infrastructure->DNS, I have mydomain.com and that domain, I can not access to navigate, which is in an external hosting.
This is qa bit clearer now. Let me rephrase it:
you are using same domain name for internal and external domain. Because of this, what you describe in Zentyal DNS covers internal machines but does not cover external ones. Am I correct ?
So you have 2 choices:
- either you change internal domain name for something different
- or you describe external servers in Zentyal DNS
Both will work and this has nothing to do with proxy ;-) Well, if you configure clients with external DNS only, no DNS cache and no HTTP proxy, enabling proxy will generate this error may push you to think that error is due to proxy but error is in fact due to DNS and confusion with domain "ownership", at least for what I understand