Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
2155 views

"Not authoritative for update Forward zone"

I'm getting this error when machines at a remote site grab a dhcp address.
The remote site does not have its own server and is on a different subnet
than the DNS and DHCP servers. The full error message is:

error: client 10.10.10.34#4639: updating zone
'museum.mdac.state.ms.us/IN': Novell DDNS : Not authoritative for update
Forward zone

DNS is on a cluster (NW65 SP3). The 10.10.10.34 address is the address of
the node DNS happens to be running on. The address for the DNS virtual
server is different. The subnet the DNS server is on is the primary zone
and the subnet having the problems is a secondary zone.

Any thoughts? I haven't been able to find anything in Knowledgebase about
it. I've tried plugging the 10.10.10.34 address into the Allow Updates
control list and several other places with no luck.

Ken

Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: "Not authoritative for update Forward zone"

In article <A%Fse.1191$5l3.881@prv-forum2.provo.novell.com>, wrote:
> the subnet having the problems is a secondary zone
>

Is that to say that your DNS server at 10.10.10.34 is a Secondary DNS
server for that zone? If yes, it cannot be used to update DNS -- only
the Primary server for the zone can do that. And if that's the case,
then I suspect your DHCP server is giving out your DNS server's address
as the first DNS server, and the client is therefore sending its own
update of DNS info to that server.

If I'm misinterpreting your setup, please clarify it for me.

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Not authoritative for update Forward zone"

>>If I'm misinterpreting your setup

At first glance I thought you had. At second glance I realized you hadn't.
And that made me realize that the subnet having the problem shouldn't be a
secondary zone. Changed it to primary and it is happy. I knew there was a
reason I've never claimed to be a DNS expert.

Thanks!
Ken
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Not authoritative for update Forward zone"

In article <QvAte.2204$5l3.1008@prv-forum2.provo.novell.com>, Ken
Hipple wrote:
> I knew there was a
> reason I've never claimed to be a DNS expert.
>

<grin> Actually you had it right for a traditional DNS environment.
But since Novell has things stored in NDS, it breaks that model,
leading to confusion even among those who are (traditional) DNS
experts.

bd
NSC Volunteer SysOp


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.