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

DNS Slow to resolve Internet traffic

DNS running on Server 2003  Workgroup - Domain not an option at the moment....

Hi, i have set up DNS on a Windows 2003 server on a workgroup, set the system properties, computer name to NAME.local on the server and workstations and it all seems to work ok. The clients use static addresses and do register ok in DNS.
If i set a forwarder within DNS to our ISP DNS server, and on the clients just set the primary DNS server to our internal DNS server, ISP traffic does get resolved but seems a bit slow.
If i remove the forwarder entry to the ISP and set the clients alternate DNS server to the ISP DNS address then the websites resolve a lot quicker.

My question is, will the client only try to register its DNS details with the primary address or will it also try and register its details with the alternate address causing more trafffic.
Am i causing any problems if i leave it like this?

The DNS is running on a HP Proliant ML350 G4  Intel Xeon 3.2GHZ with 2GB RAM.

regards
Rick
0
Rick_Penney
Asked:
Rick_Penney
  • 4
  • 3
1 Solution
 
Jaroslav LatalMSPCommented:
Hello Rick_Penney,

how many clients do you have?

It should be set as follows:
- clients points to internal DNS server
- on DNS servers network adapter set localhost as DNS server
- there is no reason to use DNS forwarder, just root servers

On a DNS server run "dnsdiag".


Regards,
Jarda
0
 
Rick_PenneyAuthor Commented:
Hi Jarda
Many thanks for your help.
We have about 90 clients at this site.
If i remove all forwarders and leave it so root hints resolve, then its ok.
I did have 2 additional forwarders added as we have 2 other subnets that i need to resolve names for.
Does the resolution look at the forwarders first and then root hints afterwards.
Its definately slower if i have the entries for the other two subnets listed as forwarders.

Or am i better off with a WINS server to look after all 3 subnets and use the DNS just for web traffic?

I havent got the support tools installed at the moment so i cant run a dnsdiag, what results will that have given me?
many thanks
Rick.
0
 
Jaroslav LatalMSPCommented:
Hello Risk,
sorry, WINS is out of my knowledge..
The best solution is to synchronize DNS entries across all 3 subnets, but in non domain environment it is not easy.

Do you have VPN between the sites?

Jarda
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
Rick_PenneyAuthor Commented:
Hi
All 3 sites are connected via MPLS. (no vpn)
If i add the DNS server entries for the other two sites into the forwarders section i can resolve across the WAN, if i dont have the entries in place i can't.
I guess the clients are slower at getting web addresses resolved as the 3 DNS servers check first before root hints resolve?
i really appreciate your time with this.
many thanks
0
 
Jaroslav LatalMSPCommented:
Rick,
Yes, clients are slow because the DNS forwarders. Probably get a responses from the offsite DNS servers..
No VPN, no domain... Sorry, I see no solution in this case.

Jarda
0
 
Rick_PenneyAuthor Commented:
Many thanks for all your help
0
 
Rick_PenneyAuthor Commented:
Just thought i'd update this.
I removed the forwarders and set up stub zones for the other subnets.
Works perfectly
Rick.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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