After you have copied the original /local/primary.tcc to
/local/secondary.tcc,
just change the word 'primary' to 'secondary' in each line.

Then check the www virtual address and the new mail addresses.

Regards,
Peter


On Tue, 2002-10-29 at 07:23, John Nichel wrote:
> Steve,
> 
>    I'm fairly lost here.  I added the second zone, and then copied the 
> primary.tcc file over to secondary.tcc, and made these changes....
> 
> $TTL 3D
> @       IN      SOA     ns.primary.tcc. jnichel.primary.tcc. (
>                          199802151       ; serial, todays date + todays 
> serial #
>                          8H              ; refresh, seconds
>                          2H              ; retry, seconds
>                          4W              ; expire, seconds
>                          1D )            ; minimum, seconds
> ;
>                  NS      ns              ; Inet Address of name server
>                  MX      10 mail.primary.tcc.     ; Primary Mail Exchanger
>                  MX      20 mail.primary.tcc.   ; Secondary Mail Exchanger
> ;
> localhost       A       127.0.0.1
> ns              A       11.11.68.3
> mail            A       11.11.68.3
> 
> www             CNAME   secondary.tcc.
> 
> www             A       11.11.68.3
>                  MX      10 mail
> 
> These two domains are on the same box.  I reloaded named, and did a dig 
> on secondary.tcc, and got nothing.  If this was C or Perl, I'd be in my 
> element. :(
> 
> Cowles, Steve wrote:
> >>-----Original Message-----
> >>From: John Nichel
> >>Subject: DNS & Bind
> >>
> >>
> >>Hi guys and gals.  I have recently been "promoted" to network 
> >>admin at my place of employment (there were only two of us at
> >>my work who even knew what a network card is, and the other
> >>quit).  Anywho, I have bind 9.1.3 setup on our primary name
> >>server, and have it working fine for our primary domain name.
> >>What I want to do is add other domains for internal,
> >>developmental use.  Our company has 8 different domain web 
> >>sites, and I'm setting up dev boxes for each one of these.  I 
> >>have the main one set up, but I don't want to have to set up
> >>a name server for each domain (I know one DNS machine can
> >>handle quite a few domain names).
> >>
> >>My nameserver is set up with a /etc/named.conf like this....
> >>
> >>// generated by named-bootconf.pl
> >>
> >>options {
> >>         directory "/var/named";
> >>};
> >>
> >>//
> >>// a caching only nameserver config
> >>//
> >>controls {
> >>         inet 127.0.0.1 allow { localhost; } keys { rndckey; };
> >>};
> >>zone "." IN {
> >>         type hint;
> >>         file "named.ca";
> >>};
> >>
> >>zone "localhost" IN {
> >>         type master;
> >>         file "localhost.zone";
> >>         allow-update { none; };
> >>};
> >>
> >>zone "0.0.127.in-addr.arpa" IN {
> >>         type master;
> >>         file "named.local";
> >>         allow-update { none; };
> >>};
> >>
> >>zone "primary.tcc" {
> >>         type master;
> >>         notify no;
> >>         file "local/primary.tcc";
> >>};
> >>
> >>include "/etc/rndc.key";
> >>
> >>The zone file for primary.tcc looks like this....
> >>
> >>$TTL 3D
> >>@       IN      SOA     ns.primary.tcc. hostmaste.primary.tcc. (
> >>                         199802151       ; serial, todays 
> >>date + todays 
> >>serial #
> >>                         8H              ; refresh, seconds
> >>                         2H              ; retry, seconds
> >>                         4W              ; expire, seconds
> >>                         1D )            ; minimum, seconds
> >>;
> >>                 NS      ns              ; Inet Address of name server
> >>                 MX      10 mail.primary.tcc
> >>;
> >>localhost       A       127.0.0.1
> >>ns              A       11.11.68.3
> >>mail            A       11.11.68.3
> >>
> >>www             CNAME   ns
> >>
> >>admin           A       11.11.68.3
> >>                 MX      10 mail
> >>
> >>Now, from any box in the company I can hit the webservs fine at 
> >>www.primary.tcc and admin.primary.tcc
> >>
> >>What I want to do is set up other doamins (like www.secondary.tcc, 
> >>admin.secondary.tcc, www.somedomain.tcc, etc.) located on 
> >>other boxes, using the main nameserver.  I know how to set up the
> >>Apache virtual hosts for this, but I just can't get the name server
> >>to work right. Normally, I would read, and mess around with it until
> >>I got it, but it took me since thursday to get the nameserver
> >>working for the primary domain, and I'm on a deadline (not to
> >>mention the fact that I'm a programmer, and not an admin).  Is there
> >>someone out there who knows how I need to configure this?
> >> Thanks.
> > 
> > 
> > If I understand your post correctly, then...
> > 
> > Duplicate your zone definition for primary.tcc in your named.conf file and
> > rename it to (for example) somedomain.tcc. 
> > 
> > You will also have to create the somedomain.tcc zone file along with making
> > the necessary changes (like SOA/A/NS/MX records). Something like:
> > 
> > zone "primary.tcc" {
> >          type master;
> >          notify no;
> >          file "local/primary.tcc";
> > };
> > 
> > zone "somedomain.tcc" {
> >          type master;
> >          notify no;
> >          file "local/somedomain.tcc";
> > };
> > 
> > Steve Cowles
> > 
> > 
> > 
> 
> 
> 
> 
> -- 
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe
> https://listman.redhat.com/mailman/listinfo/redhat-list





-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to