dns on lan, without registered ip or domain name

I have about 10 host on my lan connected to the internet via my
Slackware server which acts as a gateway and is connected to a ADSL
router. All hosts currently have static ip's and i am wanting to
implement DHCP.

I guess that by using DHCP, I would then require some other protocol /
service for address resolution, namely DNS.

If I do not have a registered domain name or ip address, could I still
implement DNS "illegaly" on our LAN? and which DNS service would be
recommended (Tiny or Bind)?

> I have about 10 host on my lan connected to the internet via my
> Slackware server which acts as a gateway and is connected to a ADSL
> router. All hosts currently have static ip's and i am wanting to
> implement DHCP.
>
> I guess that by using DHCP, I would then require some other protocol /
> service for address resolution, namely DNS.
>
> If I do not have a registered domain name or ip address, could I still
> implement DNS "illegaly" on our LAN? and which DNS service would be
> recommended (Tiny or Bind)?

Look at dnsmasq. It will act as both a DHCP server for your LAN, and a
cacheing DNS forwarder. That means that it will answer DNS queries
from /etc/hosts, from DHCP leases, and from cache. If it can't answer from
any of those, then it sends the query upstream to the real DNS servers, and
caches the result for next time. It's ideal for LAN use.

http://thekelleys.org.uk/dnsmasq/doc.html

--
To reply by email, change "deadspam.com" to "alumni.utexas.net"

Andrew Schulman wrote:
> Look at dnsmasq. It will act as both a DHCP server for your LAN, and a
> cacheing DNS forwarder. That means that it will answer DNS queries
> from /etc/hosts, from DHCP leases, and from cache. If it can't answer from
> any of those, then it sends the query upstream to the real DNS servers, and
> caches the result for next time. It's ideal for LAN use.
>
> http://thekelleys.org.uk/dnsmasq/doc.html

Much thanks for the pointer!