Setting up an internal network DNS server

Hello,
I'd like to use my Linux box as a BIND server for my internal network.
I'd like for users to be able to to access, say, server1 instead of
192.168.1.22 . I've searched through a ton of DNS documents but I
can't
find out how to do this specifically, all the docs I've found are
focused on setting up servers for the rest of the world or for a
network that already has a FQDN (which I do not) Could you give
me some pointers on how to do this?
Thanks,
Harold

On 22 Aug 2003 07:44:32 -0700, NOSPAM <(E-Mail Removed)> wrote:
> (E-Mail Removed) (David Efflandt) wrote in message news:<(E-Mail Removed)>...
>> On 21 Aug 2003 19:51:59 -0700, NOSPAM <(E-Mail Removed)> wrote:
>> > Hello,
>> > I'd like to use my Linux box as a BIND server for my internal network.
>> > I'd like for users to be able to to access, say, server1 instead of
>> > 192.168.1.22 . I've searched through a ton of DNS documents but I
>> > can't
>> > find out how to do this specifically, all the docs I've found are
>> > focused on setting up servers for the rest of the world or for a
>> > network that already has a FQDN (which I do not) Could you give
>> > me some pointers on how to do this?
>>
>> It is not much different for local DNS than for public DNS, the difference
>> being that locally, you can do whatever you want to. Just make sure that
>> the local domain you pick is either one you own, or something bogus that
>> cannot possibly be registered. For example the private domain in RedHat
>> is typically localdomain and in SuSE is simply local. Example of local
>> forward and reverse zones added to named.conf:
>>
>> zone "localdomain" in {
>> type master;
>> notify no;
>> file "pz/localdomain.zone";
>> };
>>
>> zone "1.168.192.in-addr.arpa" in {
>> type master;
>> notify no;
>> file "pz/1.168.192.zone";
>> };
>>
>> Then just follow the DNS HOWTO for setting up the zone files using
>> existing localhost and 0.0.127.in-addr.arpa zones from your bind as
>> examples of anything that might be different. NOTE: pay attention to when
>> you use a trailing dot or not for a name in a zone file.
>
> Could I do something like claiming to be a root server so that instead
> of acessing server1.localdomain I could just acess server1 (since
> server1 isn't a valid TLD). I'm new to bind, so if this is a stupid
> question, well, at least I tried

You would simply put the following in your /etc/resolv.conf:

search localdomain

Then it would try to resolve a simple hostname in your localdomain.

--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/