From Newsgroup: comp.protocols.dns.bind

--00000000000058e0af05a9fe7a3f
Content-Type: text/plain; charset="UTF-8"

Hi,

I have configured bind with IPV6 support enabled. However bind does not
listen to IPV6 address. Any particular reason.is there any place to enable
IPV6 support other than named.conf.

Version : BIND 9.11.4-P1 (Extended Support Version)


in named.conf file

listen-on-v6 { any; };


regards
DT

--00000000000058e0af05a9fe7a3f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br><div>I have configured bind with IPV6 support = enabled. However bind does not listen to IPV6 address. Any particular=C2=A0=
<a href=3D"http://reason.is">reason.is</a> there any place to enable IPV6 s= upport other than named.conf.</div><div><br></div><div>Version : BIND 9.11.= 4-P1 (Extended Support Version)<br></div><div><br></div><div><br></div><div= >in named.conf file</div><div><br></div><div>listen-on-v6 { any; };<br></di= v><div><br></div><div><br></div><div>regards</div><div>DT</div></div></div>

--00000000000058e0af05a9fe7a3f--
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.protocols.dns.bind

On 09/07/2020 11:01, Duleep Thilakarathne wrote:

Hi Duleep,

I have configured bind with IPV6 support enabled. However bind does not listen to IPV6 address. Any particular reason.is there any place to enable IPV6 support other than named.conf.

Version : BIND 9.11.4-P1 (Extended Support Version)

in named.conf file

listen-on-v6 { any; };

This should work. But how do you know that BIND does not listen on IPv6 addresses? Did you check using "ss -lunp" or "netstat -upan"?

Regards,
Anand
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.protocols.dns.bind

--00000000000017169c05aa0014cd
Content-Type: text/plain; charset="UTF-8"

Hi Anand,

Yes netstat -upan only shows only ipv4 address listen :53. But sever
listens for ipv6 SSH port. So i can confirm IPV6 working fine in server.
But not for udp port 53.

Regards
DT

On Thu, 9 Jul 2020, 14:58 Anand Buddhdev, <anandb@ripe.net> wrote:

On 09/07/2020 11:01, Duleep Thilakarathne wrote:

Hi Duleep,

I have configured bind with IPV6 support enabled. However bind does not listen to IPV6 address. Any particular reason.is there any place to

enable

IPV6 support other than named.conf.

Version : BIND 9.11.4-P1 (Extended Support Version)

in named.conf file

listen-on-v6 { any; };

This should work. But how do you know that BIND does not listen on IPv6 addresses? Did you check using "ss -lunp" or "netstat -upan"?

Regards,
Anand

--00000000000017169c05aa0014cd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi Anand,<div dir=3D"auto"><br></div><div dir=3D"auto">Ye=
s netstat -upan only shows only ipv4 address listen :53. But sever listens = for ipv6 SSH port. So i can confirm IPV6 working fine in server. But not fo=
r udp port 53.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Regards= =C2=A0</div><div dir=3D"auto">DT</div></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Thu, 9 Jul 2020, 14:58 Anand Buddh= dev, &lt;<a href=3D"mailto:anandb@ripe.net">anandb@ripe.net</a>&gt; wrote:<= br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde= r-left:1px #ccc solid;padding-left:1ex">On 09/07/2020 11:01, Duleep Thilaka= rathne wrote:<br>

Hi Duleep,<br>

&gt; I have configured bind with IPV6 support enabled. However bind does no= t<br>
&gt; listen to IPV6 address. Any particular <a href=3D"http://reason.is" re= l=3D"noreferrer noreferrer" target=3D"_blank">reason.is</a> there any place=
to enable<br>
&gt; IPV6 support other than named.conf.<br>
&gt; <br>
&gt; Version : BIND 9.11.4-P1 (Extended Support Version)<br>
&gt; <br>
&gt; in named.conf file<br>
&gt; <br>
&gt; listen-on-v6 { any; };<br>

This should work. But how do you know that BIND does not listen on IPv6 <br=

addresses? Did you check using &quot;ss -lunp&quot; or &quot;netstat -upan&= quot;?<br>

Regards,<br>
Anand<br>
</blockquote></div>

--00000000000017169c05aa0014cd--
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.protocols.dns.bind

On 09/07/2020 12:56, Duleep Thilakarathne wrote:

Hi Duleep,

After starting BIND, can you examine its log entries? It should print
all the addresses it is binding to, eg:

09-Jul-2020 13:50:57.674 listening on IPv4 interface lo0, 127.0.0.1#53 09-Jul-2020 13:50:57.676 IPv6 socket API is incomplete; explicitly
binding to each IPv6 address separately
09-Jul-2020 13:50:57.676 listening on IPv6 interface lo0, ::1#53
09-Jul-2020 13:50:57.677 listening on IPv6 interface lo0, fe80::1%1#53 09-Jul-2020 13:50:57.678 listening on IPv6 interface en0, fe80::46f:4f61:8541:6b2f%4#53
09-Jul-2020 13:50:57.679 listening on IPv4 interface en0, 192.168.178.20#53 09-Jul-2020 13:50:57.680 listening on IPv6 interface en0, 2001:1c04:2a11:7d00:1cb9:6e7e:d4b3:ae1b#53
09-Jul-2020 13:50:57.681 listening on IPv6 interface en0, 2001:1c04:2a11:7d00:61ed:2e3:3afc:b116#53

Hi Anand,

Yes netstat -upan only shows only ipv4 address listen :53. But sever
listens for ipv6 SSH port. So i can confirm IPV6 working fine in server.
But not for udp port 53.

--- Synchronet 3.21d-Linux NewsLink 1.2