• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 684
  • Last Modified:

TMG ISP Redudancy and DNS

Hello Experts,

actually this is the continuation of my previous question

Hello,

I have installed TMG with 3 NICs such as ISP1, ISP2 and Internal

I configured the ISP1 and ISP2 interfaces with IP addresses and default gateways and

configured internal NIC with IP address, but no  Default Gateway.

I installed DNS service on TMG and configured the forwarders pointing to ISP DNS servers.

Finally Internal NIC DNS configuration as follows

Primary : 127.0.0.1

Alternative: Internal AD DNS servers

Configured persistent routes

=============================================================
Persistent Routes:
  Network Address          Netmask             Gateway Address  Metric
         10.0.0.0               255.0.0.0                      10.1.2.1            1                  ( Internal LAN)
          1.1.1.1            255.255.255.255             192.168.5.1       2                   ( ISP1 DNS Server)
           2.2.2.2           255.255.255.255             192.168.4.2       3                    ( ISP2 DNS Server)
           0.0.0.0                 0.0.0.0                       192.168.4.2    Default
           0.0.0.0                 0.0.0.0                       192.168.5.1  Default

Suddenly I started facing a problem that web proxy client receiving a pop up Authentication Required.

I tried nslookup on TMG server for my domain domain but cannot resolved.

I would highly appreciate any help.


Thanks
0
cciedreamer
Asked:
cciedreamer
  • 7
  • 4
1 Solution
 
cciedreamerAuthor Commented:
I uninstall TMG and removed the server from the domain.

When I am trying to rejoin, it says the domain name cannot be resolved and the failed to join to domain

Still the interface and route configuration remain as mentioned above.

Thanks
0
 
Craig BeckCommented:
You don't particularly need DNS server to be installed on the TMG if you only want it to resolve hostnames for web clients.

The TMG server will use the DNS server addresses you configure on the internal NIC (or External NIC) to resolve URLs on the client's behalf.  The DNS server is only necessary if you want to forward internal URLs to your internal hosts/DNS servers.
0
 
Craig BeckCommented:
When you create your static routes, you don't need to change the metrics for the ISP DNS servers.  You only need to adjust the metrics for your default backup route for ISP redundancy.

So according to your routing table...
Persistent Routes:
  Network Address          Netmask             Gateway Address  Metric
         10.0.0.0               255.0.0.0                      10.1.2.1            Default            
          1.1.1.1            255.255.255.255             192.168.5.1       Default            
           2.2.2.2           255.255.255.255             192.168.4.2       Default            
           0.0.0.0                 0.0.0.0                       192.168.4.2       Default
           0.0.0.0                 0.0.0.0                       192.168.5.1       10
...might work better.

The primary DNS server always needs to go via ISP2, while the secondary DNS server always needs to go via the ASA, so these metrics are always going to be 1 as they will never need to go over the other ISP's link.

The primary route to the internet may change though, so the metric should be 1 for the ISP2 link, but lower for the ISP1 link.  Here I have set it to 10.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
cciedreamerAuthor Commented:
Sir,

What is your recommedation for DNS ? Actually I dont keep any ISP's DNS server forwarder on my internal DNS server

Thanks
0
 
Craig BeckCommented:
Your internal DNS server should use your ISP DNS servers as forwarders to ensure you get a fast response.  You don't have to use forwarders though, but if you don't you must use the Root servers or you won't resolve any external URLs.
0
 
cciedreamerAuthor Commented:
How about this if I configure a conditional forwarder on TMG server and to forward DNS request to  internal DNS Server which is responsible for AD.
0
 
Craig BeckCommented:
If you need internal clients to get to internal web sites then that's fine as the TMG will be proxying, but if you don't need any internal clients to get to internally-hosted websites there's not much point in running DNS on the TMG unless you want to manipulate URLs (block access to sites using DNS, etc).
0
 
cciedreamerAuthor Commented:
So far now everything is working.

Just a summary

- Installed the DNS service on TMG.
- Configured the forwarders pointing to ISP 1 & 2 DNS servers.
- Configured the conditional forwarder to forward DNS request to internal DNS server for AD authentication.
- Internai NIC DNS

Primary : 127.0.0.1 ( local host TMG
Alternative: Internal DNS servers.
0
 
cciedreamerAuthor Commented:
Thanks craigbeck Its working fine.

But just facing some slowness browser though I have only 1 user connected

ISP1 Leased Line 15MB
ISP2 DIA   10MB

Thanks
0
 
cciedreamerAuthor Commented:
Sir,

I posted a new question with a new design. Please can you help in this.

http://www.experts-exchange.com/Networking/Network_Management/Network_Design_and_Methodology/Q_28339114.html

Thanks
0
 
cciedreamerAuthor Commented:
Thanks :)
0

Featured Post

Prepare for an Exciting Career in Cybersecurity

Help prevent cyber-threats and provide solutions to safeguard our global digital economy. Earn your MS in Cybersecurity. WGU’s MSCSIA degree program curriculum features two internationally recognized certifications from the EC-Council at no additional time or cost.

  • 7
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now