I have set up forwarders and I have had the server running on one DNS - this does not work.
Main Topics
Browse All TopicsI have installed a Windows 2003 SBS everything is fine except for the DNS resulting in client log ons being painfully slow.
I cannot even do an NSLOOKUP on the server itself this results in -
C:\Documents and Settings\Administrator>nsl
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.0.10: Timed out
Default Server: UnKnown
Address: 192.168.0.10
The Ip settings for the machine are -
Windows IP Configuration
Host Name . . . . . . . . . . . . : orwsrv01
Primary Dns Suffix . . . . . . . : orwell.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : orwell.local
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrate
r
Physical Address. . . . . . . . . : 00-0B-DB-C0-FA-17
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.10
194.168.4.100
Primary WINS Server . . . . . . . : 192.168.0.10
Please Help...........TIA
Matt Stevens
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Windows IP Configuration
Host Name . . . . . . . . . . . . : orwsrv01
Primary Dns Suffix . . . . . . . : orwell.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : orwell.local
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integ
r
Physical Address. . . . . . . . . : 00-0B-DB-C0-FA-17
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.10
Primary WINS Server . . . . . . . : 192.168.0.10
C:\Documents and Settings\Administrator>nsl
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.0.10: Timed out
Default Server: UnKnown
Address: 192.168.0.10
>
Although it hasn't solved your problem yet that is the correct configuration. Incidentally you should have 2 NIC's in your server and put the second one on to the internet. I don't think that is causing your problem though.
I take it the nslookup command you are trying is nslookup orwsrv01?
clear the cache before you try again.
Type
ipconfig /flushdns
ipconfig /registerdns
then try the nslookup again.
Can you try the same command from a workstation.
Try nslookup and a workstation name
Check the DNS zone for what entries it has for your server name. Make sure there are no silly entries (incorrect ip address)
Silly question but check the DNS Server service is actually running.
Also check the DNS event log for any errors or warnings that might help.
check you have followed the instructions for dns setup at http://support.microsoft.c
Failing that I would recommend that you just delete the DNS zone and recreate it.
Change it to primary (non AD integrated)
Delete it
Create it again (AD integrated)
restart the netlogon service
One note above, you do not need DNS forwarders for Internet Name resolution and unless you are running clustering or a large network you won't get a speed increase from Multiple NICs.
The way MS designed the DNS is for the DNS Server to point to itself only. All other servers and workstations point to the internal DNS server only. When a request for resolution hits the server, it checks if it has it in it's database or in the Cache. If not, then it queries the Internet Root Servers for resolution, returns the results and adds them to the cache. The only time you should use forwarders is if your ISP requires it or if you need to eak the last small iota of bandwidth out of a line. Typically I see networks with forwarders that won't work any other way, but that is usually because the machine was not connected to the Internet when built, so a DNS zone beginning with a . (period) is created and that will never work without forwarders. The solution is to delete the zone starting with the . and restart. Life is good then.
Remember, use the Kiss method.
Multiple NIC's was not for speed increase but best practice for SBS setup as you run ISA or Firewall on the SBS server to provide an extra layer between the internet and your LAN.
If you don't use DNS forwarders then you use the root servers. Using forwarders reduces the load on the root servers and offloads the query to your ISP rather than your server.
KISS usually stands for Keep It Simple Stupid.
Can you report back from my suggestions please. In general you should always go for purpose designed server hardware. I would stick with a separate NIC rather than onboard anyway. Other than that you shouldn't have DNS problems from using a workstation rather than a server. Further to lrmoore's suggestion to create a PTR record you will need to make sure you have a reverse lookup zone in the DNS manager as well as the forward lookup zone. If you haven't got one. Create it using the wizard.
PS. Some more suggestions for KISS http://www.acronymfinder.c
Another place to look, is on the workstation itself that is having a problem. Pull up an ipconfig /all. I had an old network that somewhere was getting an automatic entry in DNS for a server that no longer existed, even though the only DHCP server on the network showed the correct settings. I had to put a manual entry in the DNS for the workstations to get it to stick.
Give us more details about your environment, such as what firewall/router are you using and its configuration as well as your isp, do you have a static ip? Who is running DHCP? or are all the machines static?
Have you looked at the specs of the station you are running the server on, does it have enough output?
Business Accounts
Answer for Membership
by: CaltorPosted on 2005-03-01 at 03:25:51ID: 13427976
Hi mcsmmcsm,
Take out the second DNS entry from the LAN connection properties. The SBS should only ever point to itself for DNS. If you need internet DNS resolution you need to configure DNS forwarders.
Cheers!