Anonymous_User Absent Member.
Absent Member.
1343 views

Select Timeout, zonein aborted/Error during zone-in of zone....

We are attempting to do a zone transfer with a primary DNS server
(Microsoft) in another location/separate network. On our Netware 6.03 box
we have created a zone, budget, as a Secondary zone, inputting the ip
address of the primary DNS server in the appropriate field. We've also
created an IN-ADDR.ARPA zone (not sure if this is necessary) as a
Secondary with the corresponding primary IP address. The DNS Server shows
it is the Zone-In Secondary in the Role field. When we start named.nlm
with the -zi budget switch we get Error during zone-in of zone budget at
the console screen, and Select Timout, zonein aborted at the named screen.

When using the primary DNS server in question as a forwarding server it
works as expected, resolving the names only it could, so the communication
is there between our server and their server. And I am told that port 53
is open. Is there anything I have not done correctly, and if not, any
ideas what else might be wrong?

Thank you.
Labels (1)
0 Likes
7 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Select Timeout, zonein aborted/Error during zone-in of zone....

It sounds like the like MS server is not configured to allow transfers
to your NW server.

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Select Timeout, zonein aborted/Error during zone-in of zone....

We're told it will allow transfers to any server any time. We're told....

Let me ask this question--does the name we assign to the zone on our NW
DNS secondary server have to relate in some way to the name of the primary
server's zone?

> It sounds like the like MS server is not configured to allow transfers
> to your NW server.
>
> bd
> NSC Volunteer SysOp
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Select Timeout, zonein aborted/Error during zone-in of zone....

Another quick question--is it necessary to create an IN-ADDR.ARPA zone if
all we are going to do are zone transfers as a secondary server?

> It sounds like the like MS server is not configured to allow transfers
> to your NW server.
>
> bd
> NSC Volunteer SysOp
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Select Timeout, zonein aborted/Error during zone-in of zone....

One new tidbit of info from a sniffer trace. It seems we're getting back
an error from the primary - "DNS Response Code = Not authoritative for
zone (9). Zone name = budget. Type=transfer of entire zone of authority."

Does this tell you anything new/different?

Thank you.

> It sounds like the like MS server is not configured to allow transfers
> to your NW server.
>
> bd
> NSC Volunteer SysOp

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Select Timeout, zonein aborted/Error during zone-in of zone....

In article <d4pSc.402$oe4.155@prv-forum2.provo.novell.com>, wrote:
> does the name we assign to the zone on our NW
> DNS secondary server have to relate in some way to the name of the primary
> server's zone?
>

Yes, they need to be identical.

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Select Timeout, zonein aborted/Error during zone-in of zone....

In article <l6pSc.403$oe4.52@prv-forum2.provo.novell.com>, wrote:
> is it necessary to create an IN-ADDR.ARPA zone if
> all we are going to do are zone transfers as a secondary server?
>

No. But if you don't, clients using your DNS server will need to rely
on the MS server for reverse lookups, which your NW server will need to
forward for them.

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Select Timeout, zonein aborted/Error during zone-in of zone....

In the DNSDHCP Management Console, is your server listed as
Authoritative for the zone? If not, change that and to be safe,
restart NAMED, then try again.

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.