setting DNS for my linux

Adrian Goins Adrian at mamamedia.com
Mon Nov 15 16:17:34 UTC 1999


you cannot run as master on an IN-ADDR.ARPA block smaller than a /24 (256
addresses).  the most you can do is run secondary and have your ISP update
the block, or use CNAME->PTR redirection to get control of the 8 addys you
have assigned to you.

setting yourself as master for a portion of a block that someone else is
running master for is a "Bad Thing." (tm)

Adrian Goins <adrian at mamamedia.com>
Website Server Manager
212.334.3277 x417


> -----Original Message-----
> From: Mardiana [mailto:mardiana at bdg.rad.net.id]
> Sent: Monday, November 15, 1999 8:21 AM
> To: bind-users at isc.org
> Subject: setting DNS for my linux
> 
> 
> I have registered a new domain called company.com. I have a 
> linux box with 8
> IP addresses that connect to the internet. I provide my own 
> NS server for my
> domain. Therefore i setup the file below :
> /etc/hosts  ---------------------------
> localhost  localhost
> 202.155.42.113 box.company.com box
> 202.155.42.118 mail.company.com mail
> 202.155.42.119 ns.company.com ns
> 202.155.42.120 ns2.company.com ns2
> /etc/resolv.conf ---------------------
> search company.com
> nameserver 202.155.42.119
> nameserver 202.155.42.120
> /etc/named.conf ---------------------
> options {
>         directory "/var/named";
> };
> zone "." {
>         type hint;
>         file "named.ca";
> };
> zone "company.com"{
>         type master;
>         file "company.com.zone";
> };
> zone "0.0.127.in-addr.arpa"{
>         type master;
>         file "named.local";
> };
> zone "42.155.202.in-addr.arpa"{
>         type master;
>         file "202.155.42.zone";
> };
> /var/named/company.com.zone ---------------------
> @               IN      SOA     box.company.com. 
> hostmaster.company.com. (
>                         1999111502 ; serial
>                         8 ; refresh
>                         2 ; retry
>                         1 ; expire
>                         1 ; default_ttl
>                         )
> @               IN      NS      ns
> @               IN      NS      ns2
> @               IN      MX     10      mail
> localhost     IN      A       127.0.0.1
> ns               IN      A       202.155.42.119
> ns2             IN      A       202.155.42.120
> mail            IN      A       202.155.42.118
> www          IN      CNAME   box
> ftp              IN      CNAME   box
> box            IN      A       209.15.54.113
> 
> /var/named/202.155.42.zone ---------------------
> @              IN      SOA     box.company.com. admin.company.com. (
>                         1999111502 ; serial
>                         28800 ; refresh
>                         7200 ; retry
>                         604800 ; expire
>                         86400 ; default_ttl
>                         )
> @               IN      NS      ns.company.com.
> @               IN      NS      ns2.company.com.
> 118             IN      PTR     mail.company.com.
> 119             IN      PTR     ns.company.com.
> 120             IN      PTR     ns2.company.com.
> 113             IN      PTR     box.company.com.
> /var/named/named.local ---------------------
> @               IN      SOA     localhost.      root.localhost. (
>                         1997022700 ; serial
>                         28800 ; refresh
>                         14400 ; retry
>                         3600000 ; expire
>                         86400 ; default_ttl
>                         )
> @               IN      NS      localhost.
> 1               IN      PTR     localhost.
> 
> All of those configuration just resolve box.company.com, 
> ns.company.com,
> ns2.company.com, and mail.company.com.
> What should i do if i want anyone can resolve the domain itself
> (company.com) beside box.company.com / ns.company.com / etc ? 
> (so i can use
> : http://company.com for my web address and @company.com for my email
> domain)
> Any help would be appreciated!
> 
> Thank you,
> Mardiana
> mardiana at bdg.rad.net.id
> 
> 


More information about the bind-users mailing list