|
Bind views allow you to have single names resolve to different IP's
depending on "who" is doing the querying. For instance: public users
get one (public) IP when they go to www.website.com, while private
users can get a private IP for the same name. Thus, they always use
the name regardless of where they are and it always works. As I understood the problem, this would be a good solution. Of course, as the OP said - "The problem is that the service registers our IP (external) address with a central server" is a bit confusing - sounds as if his problem is that the internal folks aren't being subject to the DNAT and therein lies his problem. This would certainly be solved by public/private DNS views - but there are also ways to solve that wholly within shorewall by causing DNAT rules to be applied to everyone (I found that to be problematic under some circumstances). If the problem is different, then bind views might not be a viable solution. Cheers. Vlado Peshov wrote:
--
|
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
