Date: Sun, 20 Oct 1996 18:55:30 +0000 From: Darius Moos <moos@degnet.baynet.de> To: Song Lining <sln@public.jn.sd.cn> Cc: FreeBSD-questions <questions@freebsd.org> Subject: Re: named,ppp and reboot problem Message-ID: <326A8380.975@degnet.baynet.de> References: <3269C141.41C67EA6@public.jn.sd.cn> <326A2323.2CCF@degnet.baynet.de> <326A2D05.41C67EA6@public.jn.sd.cn>
next in thread | previous in thread | raw e-mail | index | archive | help
OK,
in hosts you define your loopback as localhost or localhost.my.domain .
You did not specify a zone-file for my.domain .
Now i'll assume you want to have your own domain, say "lining.priv"
Then maybe you want a second machine in the near future to be connected
to your first, so let's make the thing a little more complete and
define a private network for the future.
Now i'll give your machine a name and an adress:
machine-name: song
private domain: lining.priv
private adress: 10.1.1.1
Now your hosts-file should look like this:
------------------------------------------
127.0.0.1 localhost.lining.priv localhost
10.1.1.1 song.lining.priv song
Your resolv.conf should look like this:
---------------------------------------
domain lining.priv
nameserver 10.1.1.1
Your named.boot looks like this:
--------------------------------
; $Id: named.boot,v 1.3 1995/03/23 08:43:02 rgrimes Exp $
; From: @(#)named.boot 5.1 (Berkeley) 6/30/90
; boot file for secondary name server
; Note that there should be one primary entry for each SOA record.
; example sortlist config:
; sortlist 128.3.0.0
directory /etc/namedb
; type domain source host/file backup file
cache . named.root
primary 0.0.127.IN-ADDR.ARPA localhost.rev
primaty 1.1.10.IN-ADDR.ARPA 10.1.1.rev
primary lining.priv lining.priv.zone
; example secondary server config:
; secondary Berkeley.EDU 128.32.130.11 128.32.133.1 ucbhosts.bak
; secondary 32.128.IN-ADDR.ARPA 128.32.130.11 128.32.133.1
ucbhosts.rev.bak
; example primary server config:
; primary Berkeley.EDU ucbhosts
; primary 32.128.IN-ADDR.ARPA ucbhosts.rev
; primary 0.0.127.in-addr.arpa pz/127.0.0
; primary localhost pz/localhost
Above i've assumed you want to have the zone- and rev-files in your
/etc/namedb-directory.
Next you need the localhost.rev file (BTW, why did you not use
--------------------------------------------------------------
"make-localhost" in /etc/namedb for this ?):
--------------------------------------------
; $Id: PROTO.localhost.rev,v 1.1 1995/03/21 16:33:44 wollman Exp
$
;
; This file is automatically edited by the `make-localhost' script in
; the /etc/namedb directory.
;
@ IN SOA song.lining.priv. root.song.lining.priv. (
1 ;serial
360000 ;refresh
300 ;retry
3600000 ;expire
360000 ) ;minimum
IN NS song.lining.priv.
in hinfo PPro-200 FreeBSD-2.1.5R
1 IN PTR localhost.lining.priv.
Next you need the 10.1.1.rev file (i've just copied the comments from
---------------------------------------------------------------------
above):
-------
; $Id: PROTO.localhost.rev,v 1.1 1995/03/21 16:33:44 wollman Exp
$
;
; This file is automatically edited by the `make-localhost' script in
; the /etc/namedb directory.
;
@ IN SOA song.lining.priv. root.song.lining.priv. (
1 ;serial
360000 ;refresh
300 ;retry
3600000 ;expire
360000 ) ;minimum
IN NS song.lining.priv.
in hinfo PPro-200 FreeBSD-2.1.5R
1 IN PTR song.lining.priv.
Next you need the lining.priv.zone file (again comments are copied from
-----------------------------------------------------------------------
above):
-------
; $Id: PROTO.localhost.rev,v 1.1 1995/03/21 16:33:44 wollman Exp
$
;
; This file is automatically edited by the `make-localhost' script in
; the /etc/namedb directory.
;
@ IN SOA song.lining.priv. root.song.lining.priv. (
1 ;serial
360000 ;refresh
300 ;retry
3600000 ;expire
360000 ) ;minimum
IN NS song.lining.priv.
in hinfo PPro-200 FreeBSD-2.1.5R
song IN A 10.1.1.1
www-cache IN CNAME song.lining.priv.
ftp IN CNAME song.lining.priv.
ftp-cache IN CNAME song.lining.priv.
localhost IN A 127.0.0.1
Now create this files (localhost.rev, 10.1.1.rev and lining.priv.zone)
in /etc/namedb. Don't forget to set your hostname (song.lining.priv)
in /etc/sysconfig. Send named a HUP. You may want to update your
named.root file but i do not believe that there will be any changes.
That's all. This should get you running.
For further details have a look at "DNS and BIND", Paul Albitz and
Cricket Liu, O'Reilly & Associated Inc.
Darius Moos.
Song Lining wrote:
>
> The first thing I want to clarify is that I only has a dialup ppp
> connection to my ISP and no LAN.
>
> >
> > - Do you have the hosts-file configured ?
>
> /etc/hosts has no change since first installation, I copied it
> following:
>
> # $Id: hosts,v 1.5.4.4 1996/06/17 09:17:03 jkh Exp $
> #
> # Host Database
> # This file should contain the addresses and aliases
> # for local hosts that share this file.
> # In the presence of the domain name service or NIS, this file may
> # not be consulted at all; see /etc/host.conf for the resolution order.
> #
> #
> 127.0.0.1 localhost localhost.my.domain
> #
> # Imaginary network.
> #10.0.0.2 myname.my.domain myname
> #10.0.0.3 myfriend.my.domain myfriend
> #
> # According to RFC 1918, you can use the following IP networks for
> # private nets which will never be connected to the Internet:
> #
> # 10.0.0.0 - 10.255.255.255
> # 172.16.0.0 - 172.31.255.255
> # 192.168.0.0 - 192.168.255.255
> #
> # In case you want to be able to connect to the Internet, you need
> # real official assigned numbers. PLEASE PLEASE PLEASE do not try
> # to invent your own network numbers but instead get one from your
> # network provider (if any) or from the Internet Registry (ftp to
> # rs.internic.net, directory `/templates').
> #
>
> > - How did you ifconfig your ethernet-devices (IP or DNS)
>
> NO ethernet-devices
>
> > - When do you start your named (after routed/gated ?)
>
> after routed, I start named by change namedflags from "NO" to "-b
> /etc/namedb/named.boot"
>
> > - How does your resolv.conf look (not really needed for a right
> > configured named).
>
> I copied it as following:
>
> domain sdjnptt.net.cn
> #nameserver 202.102.128.68
> #nameserver 202.96.0.133
> nameserver 127.0.0.1
>
> > - How does your named.boot file look
>
> I copied it as following:
>
> ; $Id: named.boot,v 1.3 1995/03/23 08:43:02 rgrimes Exp $
> ; From: @(#)named.boot 5.1 (Berkeley) 6/30/90
>
> ; boot file for secondary name server
> ; Note that there should be one primary entry for each SOA record.
>
> ; example sortlist config:
> ; sortlist 128.3.0.0
>
> directory /etc/namedb
>
> ; type domain source host/file backup
> file
>
> cache .
> named.root
> primary 0.0.127.IN-ADDR.ARPA localhost.rev
>
> ; example secondary server config:
> ; secondary Berkeley.EDU 128.32.130.11 128.32.133.1
> ucbhosts.bak
> ; secondary 32.128.IN-ADDR.ARPA 128.32.130.11 128.32.133.1
> ucbhosts.rev.bak
>
> ; example primary server config:
> ; primary Berkeley.EDU ucbhosts
> ; primary 32.128.IN-ADDR.ARPA ucbhosts.rev
> primary 0.0.127.in-addr.arpa pz/127.0.0
> primary localhost pz/localhost
>
> > - How does your zone-files look
>
> /etc/namedb/pz/127.0.0 is:
>
> $ORIGIN 0.0.127.IN-ADDR.ARPA.
> @ IN SOA FreeBSD.jn.sd.cn.
> hostmaster.FreeBSD.jn.sd.cn. (
> 1 ;serial
> 360000 ;refresh
> 300 ;retry
> 3600000 ;expire
> 360000 ) ;minimum
> NS ns.FreeBSD.jn.sd.cn.
> 1 PTR localhost.
>
> /etc/namedb/pz/localhost is:
>
> $ORIGIN localhost.
> @ IN SOA FreeBSD.jn.sd.cn.
> hostmaster.FreeBSD.jn.sd.cn. (
> 1 ;serial
> 360000 ;refresh
> 300 ;retry
> 3600000 ;expire
> 360000 ) ;minimum
> NS ns.FreeBSD.jn.sd.cn.
> A 127.0.0.1
>
> >
> > How about more info ?
>
> I read "DNS HOWTO" for Linux and try to do some changes to the
> configuration files but I tried to use named for no more than one day,
> so there are so many details for me to study.
>
> Thanks for your help!!!
>
> Yours,
>
> Song Lining
>
> >
> > Darius Moos.
> >
--
email: moos@degnet.baynet.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?326A8380.975>