DNS and Domain question.

[CrashX]

I currently own a domain that we will call domain.com. I use zoneedit for my dns. I can register anything I want on top of domain.com, e.g. name.domain.com.

I want to keep zoneedit for what it's doing. But I would like to run some dns of my own for my network of static IP's at home. I want a Win2k box to do dns for me. I want to use a subdomain of domain.com, say home.domain.com and have everything register on top of that. So my server would be home.domain.com and my first PC would be PC1.home.domain.com.

How do I go about setting this up? Will resolution naturaly work. For example, if you were to make an HTTP request to PC1.home.domain.com, it would go through it's path and make it to zoneedit. Would zoneedit then say that it doesn't know who PC1.home.domain.com is, but it does know who home.domain.com is, cause it has a record. Here is the IP, go ask home.domain.com. If this is how it's supposed to work, then I must be doing something wrong, cause it's not working. If not, then what am I supposed to set up? Is there a record that I can add at zoneedit that tells it that home.domain.com is the nameserver of home.domain.com?

Let me know if that's too confusing. I tried to make it as simple as possible.

 

[Zach]

Setup the home box as home.domain.com, setup DNS on it, and point your home systems to use it for DNS in their configs. If you have a router or the Win2K system do DHCP, this might be easy. probably better not to though..

Just setup all your PC's on home.domain.com to have an IP, I don't know what it looks like for you though. In linux I could... just just pc1.home.domain.com IP whatevr, pc2 something else, and so on. Then give the systems the right host names, pc1 and pc2, and set their domains right, and make their IP's corrispond to what you set in home.domain.com. Also, tell the PC's to use home.domain.com to resolve DNS, or nothing will really matter.

Edit: I aint thinking straight I think.. I don't know if I answered anything. Did I?

A last tid-bit to add on: pc1 and pc2 go inside the home.domain.com record, with thier own IP addresses. Make sure the PC's use home.domain.com for DNS. If you all systems on the net to be able to resolve pc1 and pc2 correctly, you have to setup master and slave DNS zones and have people willing to do this to whatevery is hosting domain.com, or have access to do it yourself. Again, I could show you all the configs for this in linux but I have no clue how zonedit works.

 

[CrashX]

I have the PC's setup. I have DHCP running and DNS installed. But I want to know if someone pings PC1.home.domain.com, why doesn't it reply. I have a record on home.domain.com created for PC1 pointing to a good IP. But it never even resolves an IP. It's my impression that zoneedit, master of domain.com, isn't sending the request on the home.domain.com for resolution. It's simply saying that it doesn't have a record for PC1.home.domain.com and sending it back unknown.

Is there something you can set up in DNS stating that a subdomain has it's own nameserver and to go ask it?

 

[Zach]

Is domain.com itself under your control, or just your home system setup as home.domain.com? If you control both, you could make home.domain.com a slave zone pointing to the IP of your server on the machine doing the DNS for domain.com. Or, domain.com's DNS could resolve pc1.home and pc2.home, which would equal it resolving the IP's for pc1.home.domain.com. and bypassing the home.domain.com server.

The deal is that all other systems on the net have to know who to look to for DNS resolving. Each domain gets a set of servers, domain.com's DNS is done with a specific company (or by yourself and you've not said). If you want pc1.home.domain.com to resolve without having to screw with the DNS server on every machine, either domain.com's DNS has to resolve pc1.home and pc2.home, or it has to have a slave zone for home.domain.com using