Can I add DNS to my Win2k Server and bypass @home's DNS?

[Way Cool Jr.]

I have a Win2k server that shares my internet connection. If I add DNS to it, can I point my clients to that machine for DNS lookup?

 

[n0cmonkey]

Why wouldnt you be able to?

 

[Way Cool Jr.]

Ok then....If I am doing this for my home network. How much disk space would I need for all the DNS entries?

 

[n0cmonkey]

<< Ok then....If I am doing this for my home network. How much disk space would I need for all the DNS entries? >>



You wont. You will need a small amount to cache entries for a short period of time (set by your dns server?). But that could actually be done in ram if you have enough. Unless you want to setup a root server, then you need big iron. How much do you know about DNS? Im going to take a chance and say little...

 

[Way Cool Jr.]

Not very much. I know that it is part of NT, and that it does name resolution.

Is loading DNS on my server all I would have to do? Or is it more complicated than that.

 

[fastman]

Kill'em with kindness!

 

[Way Cool Jr.]

Ok, I think I got the basics of DNS, correct me if I am wrong.

If I setup DNS on my Win2k machine, and a client wants to go to say "www.yahoo.com", it will check my DNS server first. If it has an entry cached, then that is sent to the client. If it doesn't have an entry, my DNS server can look at my @home DNS servers for an entry. If it finds one at the @home DNS server, my machine caches this info for next time, and passes the info onto the client.

So in a nutshell, if my DNS can't resolve a name, I can set it for entries in @home's DNS, then cache them for later use.

Correct?

 

[Woodie]

Don't create a "root" DNS server....

BTW, this works fine for me, and I'm on dial-up.

--Woodie

 

[waddy]

i think this is what you may be looking for DNS Guide and Host file

I do this and it works great

 

[n0cmonkey]

<< Ok, I think I got the basics of DNS, correct me if I am wrong.

If I setup DNS on my Win2k machine, and a client wants to go to say "www.yahoo.com", it will check my DNS server first. If it has an entry cached, then that is sent to the client. If it doesn't have an entry, my DNS server can look at my @home DNS servers for an entry. If it finds one at the @home DNS server, my machine caches this info for next time, and passes the info onto the client.

So in a nutshell, if my DNS can't resolve a name, I can set it for entries in @home's DNS, then cache them for later use.

Correct? >>



Close. Basically, the DNS server would see if the host you are trying to get to is one of the ones it is in charge of. If not, it will go to one of the root servers. Then that root server would tell it to go to another DNS server (root servers just forward you on to a closer DNS server). That server would either tell you if it is in charge or if not pass you on to the next one. This will go on until you get to the right DNS server, the response will be sent back to you, and your DNS server will cache it. The cache will run out and it will have to do this again. Believe it or not, this is more efficient than how the net started off.

You basically start at your DNS server, it goes to the top DNS server, and then back down, much like the roots of a tree. You are at the tip of one, you go up to the top of the list.

 

[Way Cool Jr.]

Will I need a "Fully Qualified Domain Name" in order to run a DNS server this way?

 

[afropick]

I'm sorry for asking what may seem to be a dumb question, but what are the benefits of running a DNS server from a local box?

<--- Me knows little about network stuff.

 

[Way Cool Jr.]

Right now I am 10-12 hops away from my DNS server. It would speed things up if it was on my local network.

 

[n0cmonkey]

<< I'm sorry for asking what may seem to be a dumb question, but what are the benefits of running a DNS server from a local box?

<--- Me knows little about network stuff. >>



More control. Experience. Possibly quicker results. Its fun



<< Will I need a "Fully Qualified Domain Name" in order to run a DNS server this way? >>



Not externally. And there are a few DNS servers that are all caching. djbdns can be setup to do this.

 

[Way Cool Jr.]

Ok...I installed Win2k's DNS on my machine. I tried to set it up as a caching-only DNS server. But it didn't work. All of my clients kept getting "page not found" while browsing.

Does anyone have instructions on how to set it up as a caching-only dns server? The instruction on the "help" screen and MS's website aren't very helpful.

 

[n0cmonkey]

<< Ok...I installed Win2k's DNS on my machine. I tried to set it up as a caching-only DNS server. But it didn't work. All of my clients kept getting "page not found" while browsing.

Does anyone have instructions on how to set it up as a caching-only dns server? The instruction on the "help" screen and MS's website aren't very helpful. >>



I have never needed to use Windows for a DNS server. Switch to using BIND or djbdns and I could help

 

[chlywly]

I have mediaone cable modem (which is the same as @home or owned by ATT???). To get to the internet I think you have to get DNS from them unless your Dns server itself is out on the internet. You could add your dns server staticly or through DHCP for your Lan for browsing hosts on your lan but not wan. Thats how I got my 3 computers on the internet using my one server. I can use names when I try to get to another computer on my network.

 

[miguel]

This is not going to work.

For one thing, your machine does not have permission to query to higher (or lower?) level DNS servers.

ANother thing, if it's slow getting to @home's DNS servers, then you will be slow getting anywhere on the internet, so it won't give you the benefit of speed by having your DNS server local.

 

[Saltin]

Sounds like you need to enable a forwarder on your DNS box.
If you right click the server object in the DNS snap in, you bring up the properties of the server. There is a tab in there that will allow you to enable forwarders. Put in your ISP DNS, or a Root DNS server here. With this set up, your DNS will look to the assigned forwarder to resolve any query it cannot resolve.

On a side note, when you look at the forward lookup zones on your DNS server, ensure that there is not one named "."
If there is, erase it. It is a root zone, and you don't want your DNS thinking you are a root zone.

You don't need to do any of this really, unless you are just trying to learn. And as far as caching only DNS, your box, as a DNS client, will do this anyhow. Use the internet for half an hour and then bring up the command line and type in ipconfig /displaydns.

You will see what I mean.


Miguel: DNS servers do not need specific permission(s) to query other DNS servers. They all work together in that respect. What they do need permissions for are things like zone transfers.