Continious Dial-Up and Network Traffic by David
David
Thu Sep 11 15:04:50 CDT 2003
Hmmm...ISA server _uses_ DNS....with that in mind, I'll
make a few assumptions about what you might have done :
NICs on your DC should be set to look for DNS on itself
(127.0.0.1).
All Client PCs should look for DNS on your Server's
internally facing NIC IP.
With the DNS service running, and Forward & Reverse Zones
created, you set DNS to use Forwarders (your ISPs DNS
servers) or Root Hints...or both....I'll leave others to
debate which is faster, but for my part, I prefer
successful resolution, Resolver irrelevant.
Anyway, if any of your Client PCs NICs have an external
(ie : your ISPs) DNS setting, they will be looking to this
for _all_ DNS resolution, which may, or indeed, will
likely, include resources internal to your network.
As soon as one of your Client PCs attempts to access a
resource, DNS is referred to...and if someone's pointed to
outside, this will explain the dial-up triggers.
If you need an assist with which Properties boxes you need
to do all this in, drop me a line.
_____
David
>-----Original Message-----
>I am guessing that my problem lies with ISA.
>
>I am having a problem with the network traffic on the
server side which seem
>to bottleneck when connected to the internet.
>
>From what I can understand the problem lies with the
setting on ISA that
>when a client make a request to the local network, the
request is sent to
>the internal and external server.
>
>The solution apparently is to set ISA to use only
internal DNS. The internal
>DNS must therefore be configured as a client ISA server.
This server must
>then be configured to fwd any unresolved name to an
external DNS.
>
>This sound like my problem - I am just battling to find
out exactly where
>and how to configure these settings.
>
>If there are other areas I should look at please advise.
>
>It would also help if I knew hwere to look to find out
why the dial-up is
>takin place - I must admit I am guessing that this is the
cause.
>Brian
>
>
>.
>