Anonymous_User Absent Member.
Absent Member.
965 views

Multiple forwarders don't work as expected

I recently added a 2nd forwarder to resolve names for a Win2k3 AD domain. I am
unable to resolve names for the Win2k3 AD domain. I am testing via NSLOOKUP
directly on our Netware DNS server.

Do forwarders on Netware work differently than forwarders on Windows Server? I
am expecting that name requests will be tried on each forwarder until an answer
is found. Or, are name requests being tried only on the first forwarder that is
"up"?

-Eric


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

Re: Multiple forwarders don't work as expected

In article <3KnNf.1253$oh5.1214@prv-forum2.provo.novell.com>, Eric Young
wrote:
> Or, are name requests being tried only on the first forwarder that is
> "up"?
>

I believe that is the case. But check to see if there are any settings
wrt recursion and test them out if so. If you need further follow-up
from folks here, post the version of NW and NAMED that you're running.

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Multiple forwarders don't work as expected

This is Netware 6.5 SP5, NAMED.NLM 6.04.15.

I think we are needing the Windows Server behavior here 😞 I don't know how it
should work per RFC. Maybe the Novell way is working per RFC and MS way is not.

Have tried changing recursion settings (there are no less than 3) with no luck.

-Eric

"Brad Doster" <bd@NSCSysOps.net> wrote in message
news:VA.0000379b.2d1b37e4@nscsysops.net...
> In article <3KnNf.1253$oh5.1214@prv-forum2.provo.novell.com>, Eric Young
> wrote:
>> Or, are name requests being tried only on the first forwarder that is
>> "up"?
>>

> I believe that is the case. But check to see if there are any settings
> wrt recursion and test them out if so. If you need further follow-up
> from folks here, post the version of NW and NAMED that you're running.
>
> bd
> NSC Volunteer SysOp
>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Multiple forwarders don't work as expected

In article <JxFNf.2046$oh5.1455@prv-forum2.provo.novell.com>, Eric Young wrote:
> Have tried changing recursion settings (there are no less than 3) with no luck.
>

Did you restart NAMED before testing each change?

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Multiple forwarders don't work as expected

Yes, a couple times for each change, and also added a couple minutes between the
unloads/reloads, to make sure eDir was syncing out the changes.

Rather than spend too much time on getting forwarders working as desired, we
decided instead to become a secondary of the zones that we needed from the
forwarders. Luckily we have a direct working relationship with the owner of
those zones.

-Eric

"Brad Doster" <bd@NSCSysOps.net> wrote in message
news:VA.000037a0.2e95d06c@nscsysops.net...
> In article <JxFNf.2046$oh5.1455@prv-forum2.provo.novell.com>, Eric Young
> wrote:
>> Have tried changing recursion settings (there are no less than 3) with no
>> luck.
>>

> Did you restart NAMED before testing each change?
>
> bd
> NSC Volunteer SysOp
>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Multiple forwarders don't work as expected

In article <Mw1Pf.4879$oh5.3250@prv-forum2.provo.novell.com>, Eric Young wrote:
> Rather than spend too much time on getting forwarders working as desired, we
> decided instead to become a secondary of the zones that we needed from the
> forwarders. Luckily we have a direct working relationship with the owner of
> those zones.
>

OK, thanks for letting us know.

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.