DNS Config

[F. Even]

...and to actually get http://yearbook working, you might have to do some
tricks on the webserver side itself.  The zone file should have an A record
for "yearbook" (or "yearbook.example.com." depending on how you are doing
it).

The individual clients should be configured to append "example.com" to the
addresses they use.  This can be done statically or through DHCP.  OR, if
you do not want to do that, if you are using Apache as a webserver, you can
configure "yearbook" as a VirtualHost and it will accomplish the same thing.
I have done this myself...typing "something" in my browser is a lot "easier"
than other things.  Actually, now that I am remembering, I actually do have
the domain on my clients automatically appending, but the problem was my
remote webserver would not recognize the request for "something" as opposed
to "something.example.com."  It just spit up the main page, so I configured
a VirtualHost for "something" also.

----- Original Message -----
From: "Kevin Darcy" <kcd at daimlerchrysler.com>
To: <comp-protocols-dns-bind at moderators.isc.org>
Sent: Monday, December 10, 2001 4:28 PM
Subject: Re: DNS Config



Steve Wright wrote:

> Hey Guys,
>
> having some major issues understanding how to config a new value into a
DNS
> Server, so any help is much appreciated.
>
> My aim is to map the host name http://yearbook to the IP Address
> 192.168.2.232.
> This is for an internal network.
>
> I know that i have to add the following zone (or something similar to the
> following zone) to the named.conf file:
> zome "2.168.192.in-addr.arpa" {
>         type master;
>         file "192.168.2.232";
>     }
>
> However, i am struggling to find the format for the file 192.168.2.232 for
> internal DNS. I have found multiple versions for external, but none for
> internal.

Whether a zone is used for "internal" or "external" is entirely contextual;
there is no difference in the format or syntax for an "external" versus an
"internal" zone file. So you should be able to use those "external" zone
file
examples for your "internal" zones.

Hopefully you realize though that the "in-addr.arpa" zones are only used for
"reverse" DNS, i.e. mapping addresses to names. So, by creating a
2.168.192.in-addr.arpa zone, you'll be able to create a mapping from the
address 192.168.2.232 to the "yearbook" name. But that won't help you at all
for mapping the name "yearbook" to the address 192.168.2.232, and that's
probably more useful to you, since it allows clients to connect to the
website
by its name. To establish a name-to-address mapping, you'd need a
"forward" zone file, i.e. one that doesn't end in "in-addr.arpa". Of course,
you wouldn't use the short name "yearbook"; you'd use something like
"yearbook.example.com", in which case the name-to-address entry (otherwise
known as an A record) would be contained in the "example.com" zone file.
Again, you should be able to use a sample of an "external" forward zone file
as a model for how your "internal" forward zone file should look.


- Kevin