DNS timeout

  • Thread starter Thread starter ALP
  • Start date Start date
A

ALP

I have static DNS entries for my clients connecting over
a VPN connection. I guess there is some latency in the
connection and the primary dns times out and the
secondary dns is used. The primary dns is the internal
DNS and the secondary DNS is the ISP which of course has
no info on internal clients. Is there any way to extend
the time the client waits on the primary DNS?

TIA
 
In
ALP said:
I have static DNS entries for my clients connecting over
a VPN connection. I guess there is some latency in the
connection and the primary dns times out and the
secondary dns is used. The primary dns is the internal
DNS and the secondary DNS is the ISP which of course has
no info on internal clients. Is there any way to extend
the time the client waits on the primary DNS?

TIA
Click to expand...
Remove the ISP's DNS entry, it is only going to be a problem being there.
 
The ISP entry needs to be there. I can't expect them to
manually enter the DNS servers everytime they want to
surf the net.
 
In
ALP said:
The ISP entry needs to be there. I can't expect them to
manually enter the DNS servers everytime they want to
surf the net.
Click to expand...
Having your ISP's DNS in the setup is not the correct way to do this, you
should configure your internal DNS to resolve internet names, otherwise your
problems will continue.
300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1
 
I understand this and that is the way it is setup
internally. Please keep in mind that this is a remote
connection and having users connect to my VPN for
Internet resolution is not the answer. I need them to use
my internal DNS when using the VPN and to use their ISP
when surfing the net. If the timout was a little longer
the primary DNS would get picked up and everything would
be good. When not using the VPN the primary would not get
picked up and they would use the secondary to surf the
net. Unless I add another internal DNS server the only
way I see is to increase the timeout. Do you have another
suggestion?
 
In
ALP said:
I understand this and that is the way it is setup
internally. Please keep in mind that this is a remote
connection and having users connect to my VPN for
Internet resolution is not the answer. I need them to use
my internal DNS when using the VPN and to use their ISP
when surfing the net. If the timout was a little longer
the primary DNS would get picked up and everything would
be good. When not using the VPN the primary would not get
picked up and they would use the secondary to surf the
net. Unless I add another internal DNS server the only
way I see is to increase the timeout. Do you have another
suggestion?
Click to expand...
Have the users using the VPN to have a different dial up set up for when
they are using the VPN and just surfing the net.
It is always going to give them a problem if the are connected to the VPN
using their ISP's DNS. When they are connected to the VPN they need to
exclusively use your DNS.
 
Guess I haven't been able to get my point across. They
are not using dial-up, they are using DSL or cable. There
is one lan setting and it has to accomodate both VPN and
Internet access.

If I could define what DNS to use depending on where they
are connecting to I wouldn't have a problem. So, is there
a way to change the timeout?
 
Back
Top