Basic intranet setup
Chris Buxton
cbuxton at menandmice.com
Wed Aug 1 22:15:42 UTC 2007
The DNS doesn't work without domains. However, there is a way to do
what you want.
Step 1: Set up a domain. Get things working using some private
domain, so that users can get to local resources with names like
"wiki.privatedomain.lan", "issues.privatedomain.lan", etc. (Change
"privatedomain" to something meaningful to you and/or your
organization.)
Then go into the resolver configuration of every machine on your LAN.
If you have a DHCP server, you can usually set this on the DHCP
server. The idea is to add a "local domain" or "default domain" to
each resolver, so that when the user types in a short name (no dots),
it gets looked up as a subdomain of the local domain. So the user
types in "wiki", and his resolver sends a DNS query for
"wiki.privatedomain.lan".
Chris Buxton
Men & Mice
On Aug 1, 2007, at 2:41 PM, John Steel wrote:
> There is a Fed6 server on the LAN running BIND. I want it to resolve
> names to any requesting LAN clients without any domains, so for
> example
> in their browser they can type "wiki", "issues" etc and these will
> return the relevant IP addresses of the machines on the LAN, who will
> then serve content accordingly. In other words, theres no mention of a
> domain. All the tutorials I've seen are geared to setting up
> domains and
> subdomains. I follow these, but can't see how I can set this most
> basic
> "non-domain" system up. Any tips please? Thanks.
>
>
More information about the bind-users
mailing list