o i have a domain bluebaron.ca
o dns is provided by a third party server domainmonger.com
o i have one server that provides all the internet services
o that same server is also the router for my internal network
o i want to put the network on the domain bluebaron.ca - i really don't care about the internal hosts being on the internet domain bluebaron.ca
o the server also provides the internal network with dns resolution
o i want the dns server to allow dynamic updating from its internal network hosts
** basically what i want is the ability to have the hosts in the network register with the bind server so that i can with a host in my network, ping by hostname and be able to resolve the address of another host in the network **

___Major Tool___

As a general rule, I don't find it likely that your DNS provider is going to allow dynamic DNS updates. If you need to permit updates, why not configure your DNS service for your domain, and configure forwarders for non-local traffic. Then you could set a domain suffix, and be on your way, if I understand you correctly.

i can't do that
last year the irapa(or something like that) blocked cable providers from being able to use their hosts as dns servers
i only care about the dns for my internal network
basically all i want to be able to do is have hosts on my internal network register with the my router's dns resolve so we can ping by the hostname that the host registers with the dns

You only need to add the entries to the local dns server for your network as well as keeping the root.hints file updated and you can use your dns server to resolve addresses on the internet or the lan. People on the internet would resolve your ip address using the registrar dns server you are paying for.

It will not be possible to have all hosts on the lan accessable on the internet unless they have valid ip addresses provided by your isp and are registered in dns provided by any company you choose to use.

With the company you register with you can choose something like this..


68.63.245.67 host1.domain.com
66.145.27.245 host2.domain.com
67.34.21.231 *.domain.com

i only care about the resolve within my network
i don't care about anything else
i want to do something like wins resolution
i want the resolve that handles my dns internally to be able to resolve hosts on my internal network internally only
internal network ONLY
i think the biggest issue i have is no one understands my issue

Your saying you want a dns server that will update as hosts are added to the network.



** basically what i want is the ability to have the hosts in the network register with the bind server so that i can with a host in my network, ping by hostname

These hostnames need to be added to the dns server "BIND" and the dhcp server and BIND must be compatible for it to work.

Basically you'll need dhcp.conf to contain something like this..

subnet 192.168.0.0 netmask 255.255.255.0 {
ddns-updates on;
range 192.168.0.101 192.168.0.200;
allow unknown-clients;
}


Linux client's interface config file..

DHCP_HOSTNAME="mybox.mydomain.com"


Some distros may be different syntax for the interface config file.

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




and be able to resolve the address of another host in the network **


When a host joins they will be able to get the hostnames from the dns server.

Providing that dhcp sets the dns to your dns server.

which domain should the computers in my internal network be on
if i have bluebaron.ca but i can't make updates should my network be on a different domain even though my internal resolution wont affect anyone else
i can create a zonefile for bluebaron or should it be localhost or 127... or should i create a new domain name for my internal network

The domain internally will not matter since the outside world will not know about it. You're in your own little world there so if you want to name it bluebaron.ca, go for it. Personally I make my local domains something blantantly local like homenet.local or something stupid like that.

Cheers,

MrKnisely

Yes, I use the same one on my LAN as the actually name, so either way it's up to you.

Just tagging along on this one. When you say "Linux clients interface config file.." Would that be something that a win-blows machine could pull as well?

thanks

Yes, you can do that in the TCP/IP properties for your interface. It would be under DNS Configuration.