[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Secondary Name Server not authoritative? (2nd Attempt)
- Subject: RE: [cobalt-users] Secondary Name Server not authoritative? (2nd Attempt)
- From: "Chris Demain" <cdemain@xxxxxxxxxxx>
- Date: Fri Dec 14 07:35:05 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Look in /etc/named.conf for allow-update:
zone "example.com" {
type master;
file "relative/path/to/named.example.com";
allow-update {127.0.0.1; ip.of.ns2.here;};
allow-transfer {dns1.ip.address; dns2.ip.address;}
};
Your record is also malformed.
CNAME must point to a host with an A record.
Here's how I make my zone files:
$TTL 3600
$ORIGIN com.
example IN SOA ns1.example.com. dnsadmin.example.com. (2001091904 10800 3600
6040800 86400 )
IN NS ns1.example.com.
IN NS ns2.example.com.
IN MX mail.example.com.
IN A 192.168.1.1
$ORIGIN example.com.
ns1 IN A 192.168.1.2
ns2 IN A 192.168.1.3
mail IN A 192.168.1.4
www IN CNAME example.com.
HTH
> > I have a raq3 as a primary name server and another box (RedHat
> > 7.1) as the secondary name server. There are about 10 domain
> > records on the raq but the RedHat keeps giving me error messages
> > for 2 of the domains:
> >
> > named[643]: notify failed: not authoritative for notify zone (REFUSED)
> >
> > I looked at the SOA records on the raq3 and it seems that it does
> > not list the secondary name server but the other 8 domains list
> > the secondary name server. Here is one of the domains which I'm
> > having a problem with:
> >
> > wppi.biz. IN SOA dns1.wppi.net. admin.dns1.wppi.net. (
> > 2001112820
> > 10800
> > 3600
> > 604800
> > 86400
> > )
> > wppi.biz. IN NS dns1.wppi.net.
> > www in cname www.wppi.com.
> >
> > Can someone tell me what I'm doing wrong and how I can get the
> > secondary name server to be authoritative? I prefer to do this
> > thru the admin web interface instead of adding it manually at a
> > command line.
> >
> > Thanks!
> >
> > SW