info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Using TMG as a DNS
6 views
Skip to first unread message
JP
May 28, 2014, 8:04:46 PM5/28/14
to
Here is my scenario and I appreciate any help with this, because I haven't been able to find a solution other than using a DNS server internally.
My TMG is set up to obtain all types of traffic through an external NIC and route it to my internal NIC.
The external NIC uses 68.239.123.12 and a subnet of 255.255.255.0
My internal is set up through TMG to use a network range of 192.168.16.100-131 and a subnet of 255.255.255.224
In my internal network I have various virtual machines that run various servers. I am able so far to redirect traffic using NATP for example:
TMg automatically routes any HTTP request to 192.168.16.100, which is the internal IP that my HTTP server listens to.
The same applies to my FTP server, but here is where I have an issue. I want to add a second FTP server and that will confuse TMG with the above set up.
I decided to use domain prefixes to solve the problem as such:
FTP:Public.MyDomain.com will be routed by TMG to 192.168.16.101
FTP:Private.MyDomain.com will be routed by TMG to 192.168.16.102
Is it possible to create a rule in TMG that will handle that or am I forced here to use a DNS on my internal network? Can you please instruct me on how to create or where to create such a rule? I have exhausted all of my efforts to no avail.
My TMG is set up to obtain all types of traffic through an external NIC and route it to my internal NIC.
The external NIC uses 68.239.123.12 and a subnet of 255.255.255.0
My internal is set up through TMG to use a network range of 192.168.16.100-131 and a subnet of 255.255.255.224
In my internal network I have various virtual machines that run various servers. I am able so far to redirect traffic using NATP for example:
TMg automatically routes any HTTP request to 192.168.16.100, which is the internal IP that my HTTP server listens to.
The same applies to my FTP server, but here is where I have an issue. I want to add a second FTP server and that will confuse TMG with the above set up.
I decided to use domain prefixes to solve the problem as such:
FTP:Public.MyDomain.com will be routed by TMG to 192.168.16.101
FTP:Private.MyDomain.com will be routed by TMG to 192.168.16.102
Is it possible to create a rule in TMG that will handle that or am I forced here to use a DNS on my internal network? Can you please instruct me on how to create or where to create such a rule? I have exhausted all of my efforts to no avail.
0 new messages