MZore Absent Member.
Absent Member.
1389 views

Does OES2015 novell-named support queries over IPV6?

Does anyone know what IPV6 functionality is included in the OES2015/OES11 versions of novell-named? I'm running a fully patched OES2015 / SLES11 SP3 server, and the named.run file indicated that novell-named is based on BIND 9.3.2 from the startup messages. (Note: anything in the form "<stuff>" below has been sanitized or summarized.)

My issue is that I'm attempting to configure novell-named to support incoming IPV6 queries. I've added...
listen-on-v6 port 53 {any; };
...directly into the options for the name server using ConsoleOne, as the option is not present in the Java DNS-DHCP console. That appears to work, as I see ...
    options {
novell_zone-list { ... <long list of zone names>... };
novell_server-dnsname "ns3. <domainname> ";
zone-statistics Yes;
additional-from-cache No;
recursion No;
listen-on-v6 port 53 {any; };
novell_server-mod-time 1455961216;
novell_server-dn "DNS_Healer.<eDir context> ";
}
... in /etc/opt/novell/named/named.conf. When novell-named loads, though, it does not appear to listen on any IPv6 addresses, as "netstat -lnput | grep named" returns...
	tcp        0      0 10.46.1.1:53            0.0.0.0:*               LISTEN      17282/novell-named
tcp 0 0 <publicIPV4>:53 0.0.0.0:* LISTEN 17282/novell-named
tcp 0 0 127.0.0.2:53 0.0.0.0:* LISTEN 17282/novell-named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 17282/novell-named
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 17282/novell-named
udp 0 0 0.0.0.0:43730 0.0.0.0:* 17282/novell-named
udp 0 0 0.0.0.0:52442 0.0.0.0:* 17282/novell-named
udp 0 0 0.0.0.0:49094 0.0.0.0:* 17282/novell-named
udp 0 0 10.46.1.1:53 0.0.0.0:* 17282/novell-named
udp 0 0 <publicIPV4>:53 0.0.0.0:* 17282/novell-named
udp 0 0 127.0.0.2:53 0.0.0.0:* 17282/novell-named
udp 0 0 127.0.0.1:53 0.0.0.0:* 17282/novell-named
udp 0 0 :::43033 :::* 17282/novell-named
... as if the listen-on-v6 was not present or ignored. I can't find anything official that indicates if novell-named supports inbound IPV6 queries, although BIND (named) has supported the function since version 9, meaning that the functionality has been present since OpenSuse 9, which includes all versions of SLES11. Here's the same netstat output with the SLES11SP3 "named" loaded on a similarly configured "named.conf" file:
	tcp        0      0 10.46.1.1:53            0.0.0.0:*               LISTEN      17622/named
tcp 0 0 <publicIPV4>:53 0.0.0.0:* LISTEN 17622/named
tcp 0 0 127.0.0.2:53 0.0.0.0:* LISTEN 17622/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 17622/named
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 17622/named
tcp 0 0 :::53 :::* LISTEN 17622/named
tcp 0 0 ::1:953 :::* LISTEN 17622/named
udp 0 0 10.46.1.1:53 0.0.0.0:* 17622/named
udp 0 0 <publicIPV4>:53 0.0.0.0:* 17622/named
udp 0 0 127.0.0.2:53 0.0.0.0:* 17622/named
udp 0 0 127.0.0.1:53 0.0.0.0:* 17622/named
udp 0 0 :::53 :::* 17622/named
... which leads me toward the idea "novell-named" (regardless of the BIND 9.3.2 message) simply isn't providing IPv6 support for inbound queries on port 53. By the way, I get the same results from "listen-on-v6 {any;};" so the "port 53" syntax isn't the issue; trying an alternate port number did not give any different results.

My goal is to provide support for IPV6, which would include inbound queries coming from IPv6 addresses, which we are seeing a greater need for as time passes. Since I know "named" DOES support this, I'm trying to confirm if (1) "novell-named" is supposed to and is broken; (2) "novell-named" does support IPv6 listens and somehow I've gotten the "listen-on-v6 {any;};" option wrong; or (3) "novell-named" doesn't support incoming IPv6 (yet) and I'm left with a choice to either (a) fail on all inbound IPv6 queries or (b) to lose eDirectory integration and use "named" instead... or some Frankensteinian-engineered mutant.

I'd like to avoid those options and stay with the standard functions, so I'm wondering if anyone else is successfully running "novell-named" to handle inbound IPv6 requests, or knows if this is a soon-to-be-fixed future implementation item.

Suggestions?

Michael Zore
Sterling Technologies Group
Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Does OES2015 novell-named support queries over IPV6?

MZore,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit http://www.novell.com/support and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.novell.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
- You might consider hiring a local partner to assist you.
https://www.partnernetprogram.com/partnerfinder/find.html

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Novell Forums Team
http://forums.novell.com


0 Likes
Knowledge Partner
Knowledge Partner

Re: Does OES2015 novell-named support queries over IPV6?

In article <MZore.7bewen@no-mx.forums.microfocus.com>, MZore wrote:
> Does anyone know what IPV6 functionality is included in the
> OES2015/OES11 versions of novell-named?


I can't find any reference for it being supported currently. General IPv6 support for OES is slated for
the next version, code named 'Vega' targeted for early 2017 (well they are hoping for late 2016, but
softare rarely is that co-operative)

Perhaps opening an SR can give you a better handle on it for DNS as well and prodding them that there
is real demand for IPv6 support there (every vote this way counts)

I am assuming many other services on this OES server are being served up on IPv6 such as I see on this
one OES11.2 system
netstat -lnput |grep ::
tcp 0 0 127.0.0.1:9005 :::* LISTEN 4466/java
tcp 0 0 :::111 :::* LISTEN 3373/rpcbind
tcp 0 0 :::80 :::* LISTEN 11111/httpd2-prefor
tcp 0 0 :::9009 :::* LISTEN 4466/java
tcp 0 0 :::22 :::* LISTEN 3903/sshd
tcp 0 0 ::1:631 :::* LISTEN 4530/cupsd
tcp 0 0 ::1:25 :::* LISTEN 5804/master
tcp 0 0 :::443 :::* LISTEN 11111/httpd2-prefor
tcp 0 0 :::5989 :::* LISTEN 3891/sfcbd
udp 0 0 :::1004 :::* 3373/rpcbind
udp 0 0 :::111 :::* 3373/rpcbind
udp 0 0 ::1:123 :::* 3927/ntpd
udp 0 0 fe80::250:56ff:fea5:123 :::* 3927/ntpd
udp 0 0 :::123 :::* 3927/ntpd


Also creating an Idea at https://ideas.microfocus.com/MFI/novell-oes/ might be useful.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please show your appreciation by
clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
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.