DNS design with netware and AD
Dirk Emmermacher
In our network we integrate a citrix farm. So we installed W2k3 machines
with AD.
Our plan was to integrate the AD server into netware enviroment.
For the moment we're running a class-C net with a zone A for the Netware
servers 6.5.8 and a zone B for AD. All machines in the netware zone A work
in several workgroups.
We run these setting because a UNC input shows the wrong result. The
\\domainname should have a sysvol directory instead of netware login
directory. We didn't find a solution to show both.
My desktop (netware zone A) is not be able to get a good answer from the
netware server.
nslookup novell.server
gaves this back:
novell.server was not found from novell.server.
The machine has a NS-record
When I ask for novell.server2 I've got the right answer.
When I do a nslookup on server console there is the same answer for
novell.server.
The resolv.cfg is configured with local address of this machine.
What can be the reason for it? I'm a little confused here.
Both dns-server are using (the same) forwarders. What's the better way
here:
a. Give both dns-server via dhcp to the clients or
b. One dns-entry via dhcp and secondary zones on dns-server?
Should we think about a dns-redesign? I'm open for all ideas to have a solid
dns enviroment.
Thanks in advance for your tips.
Best regards.
Dirk Emmermacher
Craig Johnson
happenining in your tests. Could you repost with actual IP addresses
and domain names? (You can change them a bit if you are concerned
about privacy).
Is there any DNS being done on the Windows servers?
I've set up multiple zones with NetWare and Windows servers interacting
before, and it certainly is something you can do. I'm not clear on
Zone A and Zone B, and if there are just two NetWare DNS servers, each
with two DNS zones assigned. I'm also not clear as to what is going
wrong with the UNC lookup.
Craig Johnson
Novell Support Connection SysOp
Dirk Emmermacher
Thanks for your answer.
We have one Class-C net 192.168.x.0
In this network runs a netware enviroment intranet.corp. All workstations
here uses a normal MS-Workgroup.
Last week wek implented an AD with an Domain zone corp.local.
With the \\intranet.corp its possible to see
_Admin, SYS and DATA volume.
With \\corp.local its possible to see
Netlogon. Sysvol and some printers.
For our citrixfarm we want to have all objects here. I think its possible,
but we wasn't able to set it well. We spent several hours here to a right
way.
Should we change our Netwareserver to the AD-zone.
Are there TID's for this scenario available?
Changing all servers an workstations to corp.local (Include import all
workstations to AD is a lot of work)
Best regards.
Dirk
>>> Craig Johnson<cra...@ix.netcom.com> schrieb am Freitag, 12. Februar
2010
um 19:43:
Craig Johnson
> Last week wek implented an AD with an Domain zone corp.local.
> With the \\intranet.corp its possible to see
> _Admin, SYS and DATA volume.
Are you using CIFS to see the servers?
>
> With \\corp.local its possible to see
> Netlogon. Sysvol and some printers.
>
What about adding both domains for the servers? (In the hosts files,
add on the second domain on the same line as the original domain). In
DNS, make sure you have entries for the server IP addresses in both
domains.
I'm still confused...
Dirk Emmermacher
>>> Craig Johnson<cra...@ix.netcom.com> schrieb am Mittwoch, 17. Februar
2010
um 19:44:
> In article <4B79671A.849E.00DA.1@no‑mx.forums.novell.com>, Dirk
> Emmermacher wrote:
>> Last week wek implented an AD with an Domain zone corp.local.
>> With the \\intranet.corp its possible to see
>> _Admin, SYS and DATA volume.
>
> Are you using CIFS to see the servers?
My netware servers don't use CIFS-shares.
>>
>> With \\corp.local its possible to see
>> Netlogon. Sysvol and some printers.
>>
> What about adding both domains for the servers? (In the hosts files,
> add on the second domain on the same line as the original domain). In
> DNS, make sure you have entries for the server IP addresses in both
> domains.
It is an good idea to add both zones.
Have a nice weekend :)
Dirk
Dirk Emmermacher
Thanks a lot for your answer.
Reconfiguring the DNS needs a some time. So I think we do it, when there no
larger projects to do.
For the the moment we added our netware DNS server the corp.local zone as
secondary.
After fixing some a permission problem on the DC, the name resolution
works.
What's the better way inyour eyes? Moving DNS/DHCP to the windows server or
DNS on the Windowsserver and DHCP on netware? IMHO I would prefer keep all
services on one server.
Have a nice weekend :)
Dirk
>>> magic31<mag...@no-mx.forums.novell.com> schrieb am Mittwoch, 17.
Februar
2010 um 21:16:
> Emmermacher;1933317 Wrote:
>> ...Changing all servers an workstations to corp.local ..
> Hi Dirk,
>
> I'm not sure I understand what the issue is or what you would like to
> be seeing? But it is good to work out a plan to reconfigure DNS so only
> one DNS domain is used within your network. Until then you might want
> to add both search suffixes to the resolv.conf so both dns domains are
> searched when resolving.
>
> Netware/OES2 does not really care about DNS, as long as hostname
> resolving works it should be ok.
> With a bit of planning/pre configuring it should be relatively easy to
> reconfigure the Netware servers/Netware DNS‑DHCP and your workstations
> to use corp.local instead of intranet.corp. Just make sure all hosts
> that can be resolved in intranet.corp are also resolvable and correctly
> set (forward/reverse lookup) in the corp.local DNS domain. Then
> reconfigure each server and make sure the workstations get the correct
> new settings.
>
> NOTE: A word of caution when using domain names ending with .local.
> This can cause resolving issues depending on how resolving is
> configured, mainly if multicast dns has been enabled (which is so by
> default on SLES/SLED/openSUSE/OES).
>
> If the servers are not resolving correctly (using tools like ping, etc)
> add ' mdns off ' to your /etc/host.conf & reboot the server. This is
> only necessary on your Novell Linux systems AFAIK.
>
> Cheers,
> Willem