Anonymous_User Absent Member.
Absent Member.
1103 views

dns/dhcp

After I install my first dns/dhcp server, my host can get IP and forward dns
request perfectly. But after I install my dhcp/dns servers for my other two
subnets, nothing seems to work right. For example, I cannot use the dns/dhcp
management console to manage the servers. Also, the server no longer starts
dns and dhcp automatically. The host no longer get IP. There seems to be a
conflict somewhere. While the objects are created under the same
organization, they are in different ou's on different subnets.

My question is, when adding additional dns/dhcp servers using the oes2 disk,
do I not select dns nor dhcp... but instead, just add them later using the
dns/dhcp management console?


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

Re: dns/dhcp

Specifically, do I need to select the DNS package during the install of my
other 2 servers if I want them to be Secondary Zone Types?

Same with DHCP, if I intall my 2 other servers, which are on different
subnets and separate OU's. Do I need to select the DHCP package during
install? Or do I just manage from the console?
Thanks.

"ok-linux" <postmasters@unatego.stier.org> wrote in message
news:A9%mp.27500$325.24836@kovat.provo.novell.com...
> After I install my first dns/dhcp server, my host can get IP and forward
> dns request perfectly. But after I install my dhcp/dns servers for my
> other two subnets, nothing seems to work right. For example, I cannot use
> the dns/dhcp management console to manage the servers. Also, the server no
> longer starts dns and dhcp automatically. The host no longer get IP. There
> seems to be a conflict somewhere. While the objects are created under the
> same organization, they are in different ou's on different subnets.
>
> My question is, when adding additional dns/dhcp servers using the oes2
> disk, do I not select dns nor dhcp... but instead, just add them later
> using the dns/dhcp management console?
>
>



0 Likes
Micro Focus Contributor
Micro Focus Contributor

Re: dns/dhcp

You do want to select Novell DNS and Novell DHCP for installation. This
can be done during the OES2 install or they can be added after using
Software Management or OES Installation and Configuration.

Your problem is causing by having multiple locator objects in the tree.
For DNS and DHCP management to work properly there can only be one
locator for DNS and one for DHCP. When you are doing the yast
configuration for DNS and DHCP on the second and third servers, be sure
to set the contexts for the objects to the same contexts that were used
on the first server. This way all servers will get configured on the
same locator object.

To fix it, you will want to remove the objects for the second and third
server. locator and group for DHCP and locator, group, and
rootserverinfo for DNS. You can then run "yast2 novell-dhcp" and "yast2
novell-dns" on both of those server and configure them using the same
contexts as the first server. You should then be able to manage DHCP
and DNS using the DNS/DHCP Management Console or iManager.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: dns/dhcp

If I understand this correctly, the second and third servers can have their
server objects in their own container ie NCP Server object, NDSPKI object,
LDAP, so on..., but I need to point the DNS and DHCP when YAST gives me the
list of OES2 items that will be configured after the install, to the same
container that my initial locator object in. Is this correct?

Thanks so much.



"TitanXV" <tsanford@novell.com> wrote in message
news:Yoknp.27858$325.13388@kovat.provo.novell.com...
> You do want to select Novell DNS and Novell DHCP for installation. This
> can be done during the OES2 install or they can be added after using
> Software Management or OES Installation and Configuration.
>
> Your problem is causing by having multiple locator objects in the tree.
> For DNS and DHCP management to work properly there can only be one locator
> for DNS and one for DHCP. When you are doing the yast configuration for
> DNS and DHCP on the second and third servers, be sure to set the contexts
> for the objects to the same contexts that were used on the first server.
> This way all servers will get configured on the same locator object.
>
> To fix it, you will want to remove the objects for the second and third
> server. locator and group for DHCP and locator, group, and rootserverinfo
> for DNS. You can then run "yast2 novell-dhcp" and "yast2 novell-dns" on
> both of those server and configure them using the same contexts as the
> first server. You should then be able to manage DHCP and DNS using the
> DNS/DHCP Management Console or iManager.



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: dns/dhcp

I see that nice little "reteive" button. Think I will click that and see
what happens.

"ok-linux" <postmasters@unatego.stier.org> wrote in message
news:q8lnp.27871$325.19842@kovat.provo.novell.com...
> If I understand this correctly, the second and third servers can have
> their server objects in their own container ie NCP Server object, NDSPKI
> object, LDAP, so on..., but I need to point the DNS and DHCP when YAST
> gives me the list of OES2 items that will be configured after the install,
> to the same container that my initial locator object in. Is this correct?
>
> Thanks so much.
>
>
>
> "TitanXV" <tsanford@novell.com> wrote in message
> news:Yoknp.27858$325.13388@kovat.provo.novell.com...
>> You do want to select Novell DNS and Novell DHCP for installation. This
>> can be done during the OES2 install or they can be added after using
>> Software Management or OES Installation and Configuration.
>>
>> Your problem is causing by having multiple locator objects in the tree.
>> For DNS and DHCP management to work properly there can only be one
>> locator for DNS and one for DHCP. When you are doing the yast
>> configuration for DNS and DHCP on the second and third servers, be sure
>> to set the contexts for the objects to the same contexts that were used
>> on the first server. This way all servers will get configured on the same
>> locator object.
>>
>> To fix it, you will want to remove the objects for the second and third
>> server. locator and group for DHCP and locator, group, and
>> rootserverinfo for DNS. You can then run "yast2 novell-dhcp" and "yast2
>> novell-dns" on both of those server and configure them using the same
>> contexts as the first server. You should then be able to manage DHCP and
>> DNS using the DNS/DHCP Management Console or iManager.

>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: dns/dhcp

TitanXV, thanks.. that did the trick!


"TitanXV" <tsanford@novell.com> wrote in message
news:Yoknp.27858$325.13388@kovat.provo.novell.com...
> You do want to select Novell DNS and Novell DHCP for installation. This
> can be done during the OES2 install or they can be added after using
> Software Management or OES Installation and Configuration.
>
> Your problem is causing by having multiple locator objects in the tree.
> For DNS and DHCP management to work properly there can only be one locator
> for DNS and one for DHCP. When you are doing the yast configuration for
> DNS and DHCP on the second and third servers, be sure to set the contexts
> for the objects to the same contexts that were used on the first server.
> This way all servers will get configured on the same locator object.
>
> To fix it, you will want to remove the objects for the second and third
> server. locator and group for DHCP and locator, group, and rootserverinfo
> for DNS. You can then run "yast2 novell-dhcp" and "yast2 novell-dns" on
> both of those server and configure them using the same contexts as the
> first server. You should then be able to manage DHCP and DNS using the
> DNS/DHCP Management Console or iManager.



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.