[OmniOS-discuss] dns howto

[Andries Annema]

Hi Gyu,

Maybe not a direct answer to your question, but might it be an option to 
use BIND from the 'pkgsrc' repository?
http://pkgsrc.joyent.com/install-on-illumos/

To me that repo seems quite future-proof for packages to be used in 
non-lx zones.

Regards,

Andries


On 2018-09-22 16:47, PÁSZTOR György wrote:
> Hi,
>
> Do someone have any best practice how to serve dns from omnios?
> I'm migrating my home nas from my old N54L box to a custom built nas pc.
> On the old box I have omnios 151014, where I served dns requests in my home
> lan via an old zone migrated from the earlier openindiana 151a9 zone.
> The 151a9 zone worked without any problem on the 151014 omnious without a
> problem.
> But I assume, some changes happened between 014 and 026 which broke binary
> compatibility because neither my old 014 zone, neither my old 151a9 zone
> was not able to start on the 026.
> The 014 was not a big problem, even if there were no upgrade path.
> I started with a clean zone, and moved there the other stuff (eg. nginx).
> But the dns is kind a tricky. I checked how I served dns, and it seems
> bind9 was part of the openindiana.org repo, while I was not able to find
> any dns-related solution for current omnios releases.
> I thought I'll do that with a debian9 lx zone.
> Well, it's more or less work, but this error messages worries me in bind9's
> log:
> root at dns:/var/log/bind9# tail bind.log
> 22-Sep-2018 14:39:31.166 general: error: ../../../../lib/isc/unix/socket.c:2881: unexpected error:
> 22-Sep-2018 14:39:31.167 general: error: setsockopt(520, IP_RECVTOS) failed: Protocol not available
> 22-Sep-2018 14:39:31.167 general: error: ../../../../lib/isc/unix/socket.c:2881: unexpected error:
> 22-Sep-2018 14:39:31.167 general: error: setsockopt(521, IP_RECVTOS) failed: Protocol not available
> 22-Sep-2018 14:39:44.555 general: error: ../../../../lib/isc/unix/socket.c:2881: unexpected error:
> 22-Sep-2018 14:39:44.555 general: error: setsockopt(520, IP_RECVTOS) failed: Protocol not available
> 22-Sep-2018 14:39:44.582 general: error: ../../../../lib/isc/unix/socket.c:2881: unexpected error:
> 22-Sep-2018 14:39:44.583 general: error: setsockopt(520, IP_RECVTOS) failed: Protocol not available
> 22-Sep-2018 14:39:44.711 general: error: ../../../../lib/isc/unix/socket.c:2881: unexpected error:
> 22-Sep-2018 14:39:44.711 general: error: setsockopt(24, IP_RECVTOS) failed: Protocol not available
>
> relevant logging config:
> root at dns:/etc/bind# grep -A 7 logging named.conf.options
> logging {
>          channel b_log {
>                  file "/var/log/bind9/bind.log" versions 30 size 1m;
>                  print-time yes;
>                  print-category yes;
>                  print-severity yes;
>                  severity info;
>          };
>
>
> Does anyone have any idea how to solve this?
> I already added the -4 option to /etc/default/bind9.
> I found this conversation regarding the topic:
> https://echelog.com/logs/browse/smartos/1477605600
> This is from 2 years ago, and doesn't seem helpful by now, since bind
> starts, just it dumps an insane amount of log about this protocol
> unavailable. My eyes are bleeding, I barely see what protocol is missing
> here. As I wrote, I tried the obvious: adding -4 to the options, and I see
> that amongs the running process's arguments.
>
> Thanks for every help!
>
> Regards,
> Gyu
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss