Resolving an Intranet Domain Name Via DNS & DHCP

Hello,

I have a newly installed apache server, with jakarta, MySQL and all the trimmings that is configured with 5 virtual hosts and growing on a single windows 2000 AS system on a small (10 computer) Network. I tested and used the apache server & extras via the hosts file on a single box for a year now so i know they are working right. I can also call up the apache server by using the server ip (192.168.0.1) in a web browser.

Currently I have a single Domain registered called "intra" for my intranet. I use NAT which is built in to windows for my internet connection which is a DSL line.

What I wanted seemed pretty simple: A client machine types in to their browser "avitars.intra" and resolves at the server which looks up the ip 192.168.0.1 (itself/localhost).

This then calls my apache server, etc. which serves the page. I was using a single box before and modifing the hosts file, but seeing how I have people that come and go with their laptops developing web code frequently with me, I had to move to a MS DNS and DHCP solution which is built into the windows server anyways.

--------------
In DHCP i have the scope options:
Server: 192.168.0.1, 4.2.2.1, 4.2.2.2
Router: 192.168.0.1
Domain Name: intra

--------------
In DNS i have defined in short:
Name server (NS): win2k (win2k.intra)
Zone: intra
Domain: avitar.intra
Host: avitar
NS: win2k (win2k.intra)
Domain: avitar2.intra
Host: avitar2
NS: win2k (win2k.intra)
Domain: avitar3.intra
Host: avitar3
NS: win2k (win2k.intra)

---------------

I have been using 'intra' and the DHCP for a year or so for basic networking purposes. The sever is set to resolve on the LAN server DNS, then query the ISP's Name servers.

I bought the book DNS&Bind only to find little help on the subject since most of the topics cover bind, or are geared to webservers, (which will be my next step; publishing these domains on the web in a month or 2).

I have heard quite a bit about BIND and TinyDNS, would they conflict with my normal Microsoft DNS? I am guessing they will. I just want to have a working topology.

I appreciate any help you can give me.

I should have read this thread from backward.
tinydns is not for M$
If port 53 already in use, of course there will be conflict.

I said i was using Microsoft wersions of DNS & and DHCP that come with the server.

I am not using TinyDNS OR BIND. It was more of a comment of frustration since it seems that no one is really making mention of how to do it with the MS version of DNS.

I read that post though that you mentioned today.

Just curious, why are you using Microsoft DNS Server? Don't think I'm about to attack ya for using it. Is it cause it's graphically oriented?

Well first I'm new to DNS at this level...

I previously just used it for just managing users that connected to my network.

It does also have a (pathetic) gui, but a gui none the less.

It wasn't until I started looking for material on this subject about 2 weeks ago that I found out about TinyDNS, Bind, etc. I think I have even found out how to solve this problem to a limited extent in therory, unfortunately I have no clue about how to implement it.

I am pretty sure I am going to have to remove the lame MS DNS, however it isn't something im looking forward to.

I want to make something clear though: I am no lover of microsoft software... Unfortunately I haven't had the time to get up to speed on linux or Unix for admin purposes yet... Im still at the user level for those systems.

I do have a redhat9 server that is comming in within 3 months or so... but I cant wait that long without getting this stuff outta the way.

To recap:
-I have 1 box called 'win2k' ip address 192.168.0.1 with apache MS DNS, MS Active Dir, apache, & MS NAT on it.
-'intra.win2k' seems to be the default NS of the zone 'intra'
-I have the primary zone set up called 'intra' on 'win2k'
-I have the domain called 'intra' on 'win2k'
-I set up forward and reverse lookups for this zone
-I want to set up an intranet on my network for my users for web development.

What specifically seems to be the problem are:
-first it seems that all DNS queries resolve at the ISP's NS due to NAT (discovered via nslookup)
-I don't know how to make the network first try and resolve DNS names locally, and then try with the ISP's domains.
-I am not sure what records I place under what area's to tell clients who query my NS that the domain is active.

What I think I have to do is the following; Correct me if i'm wrong:
-set up my name server as a slave of my ISP's name server. (I'm guessing Verizon may not like that.)
-I am pretty sure that I need to set up the following records (although it doesn't seem to work):



(Might want to add to the list remove MS DNS, install bind, start from scratch =)

It is because of the mystery relationship between MS DNS Server and Active Directory that I don't try to figure out what's wrong with MS DNS Server. But I do know this:

"-set up my name server as a slave of my ISP's name server. (I'm guessing Verizon may not like that.)"

1) doesn't do what you think it will
2) wouldn't work anyway

I also know that MS DNS Server SHOULDN'T have anything to say about whether it is queried before your ISP's DNS servers.

I know nothing about MS NAT.

Typically, I would ask a user to check this: "ipconfig /all" and read the DNS Servers listed and make sure that a local address is listed first.

You were right when I double checked about making my DNS server a slave.

You were wrong about it the MS DNS though.... The problem i was truely having was because I didn't turn recusioning on so it wasn't resolving my internal DNS's that I was not authoritive for.

After i did this I got the domains up and they are working great!

Thanks for your help. I still think I am going to eventually to bind since the DNS sever in windows lacks some of the RFC Standards.

"I also know that MS DNS Server SHOULDN'T have anything to say about whether it is queried before your ISP's DNS servers."

I wasn't wrong because I stated an opinion. And it just so happened that your server WAS queried before your ISP's DNS Servers (reguardless of recursion) it just wasn't working like it should.

"I still think I am going to eventually to bind since the DNS sever in windows lacks some of the RFC Standards"

Very true. I use BIND cause I prefer that software adhere to RFC standards. Standardization is the way to go for complete interoperable compatability. Microsoft is infamous for their proprietary methods. I also extremely dislike proprietary hardware in computers which is why I'll never buy a pre-built brand computer again. Same goes for DNS servers. If they don't follow standards, I don't want anything to do with them, and I think BIND best incorporates the RFC standards.