Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

dns setup

Status
Not open for further replies.

CTmtnbkr

IS-IT--Management
Dec 4, 2002
47
US
Hi

new install of win2000 server. this is the only server and is setup as a dc.

all clients use static ips.

what would be the correct dns address for this server. presently win2k set it up as 127.0.0.1 (default) the ip address of this server is 10.10.1.1.

also, i have my dsl (router) conection setup with an ip of 10.10.1.10. clients are setup using these #'s (ie 204.60.0.2 as the dns server). is this correct?

I am experiencing very slow network performance, especially with sbt pro50 a foxfpro accounting package. could the dns be affecting this?

i know....a lot of info, but any help would be appreciated.

Thanks
 
ok....i see where i am making my mistakes.

so what should I use as a dns server address on the server?
I see that the dafualt on my machine is the loopback....

should i use the ip of the server 10.10.1.1? in assuming it goes in the dns add box of the server too?

after i setup the lookup zones....how do i get my clients to get web access? where should I point them?

i am using static ips...how should client dns be setup?

thanks
 
I'd use 10.10.1.1. It can go in the TCPIP settings on the server, although the server already knows that it is the DNS server.

On your clients, I'd point their DNS to your server's IP address, 10.10.1.1. The way you have your clients set up will see queries on your *internal* network go out to your ISP's DNS server. These DNS servers know nothing about your network. This will be a great source of delay.

You'll need to configure your DNS server to forward unresolved queries to your ISP's DNS servers. Then from your clients you could ping successfully.

Your default gateway (on the clients) I'd set to be your DSL router (10.10.1.10).
 
would my incorrect dns settings cause application performance to slow signifigantly?

the reason ask is that this server upgrade to windows 2k (on a xeon 2.8 cpu) is MUCH slower than our previous setup.. which was (dont laugh)lantastic 7.0 on a 700 p3.

All other equipment other than the server is exactly the same....I dont understand...i thought performance would greatly improve..

any ideas on why this is happeneing?
 
Don't know much about your Accounts App, but if you have the main app on the server and client software on your PCs, then the DNS misconfig could have a lot to do with the slowness.

DNS is everything to Active Directory.

If your Accounts client is looking for the server, the PC will probably:
1. check hosts files firstly,
2. then it'll make a DNS query - at this point your PC will be asking your ISP. Your ISP will maybe forward the request on and up the DNS tree until it finally gives an 'I don't know' result.
3. Then your PC will broadcast your network looking for your server.

You are right, the hardware you have should make for a quick system. But there are other reasons for a slowdown, including a hardware fault (like a faulty NIC).

But at the moment DNS is the main suspect.
 
First I want to thank everyone who has provided help in this matter....i really appreciate it.

Right now in my servers dns properties, i have a value of 127.0.0.2.

im assuming this is causing some chaos as well?


should I replace it with 10.10.1.1? dont think i can leave it blank.

looks like an after hours job....this change will pop users out i think

I know... lots of questions....thanks for bearing with me

T
 
> Right now in my servers dns properties, i have a value
> of 127.0.0.2.

>im assuming this is causing some chaos as well?

It won't cause chaos and will probably have no effect (unless multihoming etc).

> would my incorrect dns settings cause application
> performance to slow signifigantly?

For example client1 requests a file from server1, client1 access server1 by resolving the IP address. In your setup the clients are looking to the internet connection to resolve and have to wait until they get no response to try the internal connection.

Ash.



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top