James Knott wrote:

IPv4 DNS servers are listed in /etc/resolv.conf.  Is there similar for IPv6 servers?

Yes, also in /etc/resolv.conf Along with IPv5, IPv7 and IPv11. -- Per Jessen, Zürich (13.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.

James Knott wrote:

On 2022-09-25 15:20, Per Jessen wrote:

...

James Knott wrote:

...

IPv4 DNS servers are listed in /etc/resolv.conf.  Is there similar for IPv6 servers? Yes, also in /etc/resolv.conf

Along with IPv5, IPv7 and IPv11.

Here's what resolv.conf shows:

nameserver 172.16.0.1 nameserver 8.8.8.8 nameserver 4.4.4.4

These are what's configured in the DHCP server.

Okay. Here is one of mine: nameserver 192.168.2.254 nameserver 2a03:7520:4c68:1::1000 -- Per Jessen, Zürich (11.4°C)

James Knott wrote:

On 2022-09-25 15:45, Per Jessen wrote:

...

Okay. Here is one of mine:

nameserver 192.168.2.254 nameserver 2a03:7520:4c68:1::1000

Does that computer use network manager?  Or static config?

That one uses wicked. I have dhcpv4 and dhcpv6 and radvd. -- Per Jessen, Zürich (13.4°C) Слава Україні! Slava Ukraini!

* James Knott [09-26-22 07:54]:

On 2022-09-26 03:10, Per Jessen wrote:

...

...

Does that computer use network manager?  Or static config? That one uses wicked. I have dhcpv4 and dhcpv6 and radvd.

So, that would be the same as my desktop system, which uses the IPv6 DNS server.  However, my ThinkPad, which uses the network manager uses IPv4, though the same computer uses IPv6 when running Windows. My Android phone also uses IPv6.  So, it appears there is a problem with network manager not using IPv6 DNS servers, whether with RDNSS or DHCPv6.  I guess I'll have to file a bug report.

there is configuration available in NetworkManager and you may assign the servers *you* desire. why not configure it instead of filing a bug report. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

* James Knott [01-01-70 12:34]:

On 2022-09-26 09:11, Patrick Shanahan wrote:

...

there is configuration available in NetworkManager and you may assign the servers*you* desire. why not configure it instead of filing a bug report.

The point is this is supposed to work and doesn't.  As mentioned, this is on a notebook computer, which can be moved to different locations.  At home, I want to use my own DNS server, as it contains local addresses that are useless elsewhere.  That DNS would not be available to me elsewhere.  Saying to manually configure something that's supposed to work automatically isn't a solution.  It works with Windows and Android, but not Leap 15.4.  Also, this problem has been around for a while with SLAAC and RDNSS.  I have only recently been able to try it with DHCPv6.  So, that's two methods that should work, but don't.

I have a Tumbleweed box utilizing NetworkManager and the default installation does not list *any* DNS servers, and correctly connects utilizing ipv6. you do not want to utilize the "default" setting but specify your own. why do you think that NetworkManager should know this w/o you specifically setting those desired sites? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

On 2022-09-26 12:13, Patrick Shanahan wrote:

I have a Tumbleweed box utilizing NetworkManager and the default installation does not list*any* DNS servers, and correctly connects utilizing ipv6. you do not want to utilize the "default" setting but specify your own. why do you think that NetworkManager should know this w/o you specifically setting those desired sites?

Resolv.conf lists the DNS server(s) available.  On my desktop computer, that info is from a static configuration in Yast. However, when network manager is used, those servers are supposed to be added automatically, through DHCP, DHCPv6 or RDNSS.  On every other device I use, an IPv6 address for the DNS server is used, except for my notebook computer, when running Leap 15.4.  That same computer uses the IPv6 address when running Windows.  So, clearly the issue is with the network manager on Leap 15.4 and earlier versions.  I have verified this by doing packet captures on my pfSense firewall/router. BTW, I was first aware of this issue 12 years ago, with RDNSS and as of yesterday with DHCPv6. Also, a Windows 10 VM running on this computer uses IPv6, while Leap uses IPv4.

On 2022-09-26 13:20, Per Jessen wrote:

James, fwiw, it works here on my laptop with Leap 15.2.

I do seem to recall some issue with the RDNSS option not being accepted, so I had to use dhcpv6 :

option dhcp6.name-servers

Where does that go?

James Knott wrote:

On 2022-09-26 13:20, Per Jessen wrote:

...

James, fwiw, it works here on my laptop with Leap 15.2.

I do seem to recall some issue with the RDNSS option not being accepted, so I had to use dhcpv6 :

option dhcp6.name-servers

Where does that go?

In your dhcpv6 server config: /etc/dhcpd6.conf -- Per Jessen, Zürich (15.2°C)

On 2022-09-26 14:05, Per Jessen wrote:

...

In your dhcpv6 server config: /etc/dhcpd6.conf

Like this for instance:

option dhcp6.name-servers = 2a03:7520:4c68:1::1000

That's for the server, not the client.  My server is in my pfsense firewall/router and works fine.  The issue is my ThinkPad, when running Leap, only uses DHCPv4 to get the DNS server address.  Other devices have used RDNSS for years without issue.  I just set up the DHCPv6 server yesterday, to see if it would work for this.  I can use IPv4 but not IPv6. I just did a test and did a packet capture for port 67 and 546.  I get both DHCP and DHCPv6 and both show the appropriate addresses, but only the IPv4 address is used.

James Knott wrote:

On 2022-09-26 14:05, Per Jessen wrote:

...

...

In your dhcpv6 server config: /etc/dhcpd6.conf

Like this for instance:

option dhcp6.name-servers = 2a03:7520:4c68:1::1000

That's for the server, not the client. 

Yup. As I wrote.

My server is in my pfsense firewall/router and works fine.  The issue is my ThinkPad, when running Leap, only uses DHCPv4 to get the DNS server address.  Other devices have used RDNSS for years without issue.  I just set up the DHCPv6 server yesterday, to see if it would work for this.  I can use IPv4 but not IPv6.

All I can say is, on 15.2, it works for me with a dhcpv6 server on the network. I'm happy to share the config. I don't know where NM stores the config information received, it's got to be there, somewhere. -- Per Jessen, Zürich (15.0°C)

On 2022-09-26 14:49, Per Jessen wrote:

All I can say is, on 15.2, it works for me with a dhcpv6 server on the network. I'm happy to share the config. I don't know where NM stores the config information received, it's got to be there, somewhere.

Well, show me what you have.  However, I think I will file a bug report.  This shouldn't be so difficult for something that's supposed to be automatic. At least, I can provide the server name via DHCPv4 and that resolves to an IPv6 address.

James Knott wrote:

On 2022-09-26 14:49, Per Jessen wrote:

...

All I can say is, on 15.2, it works for me with a dhcpv6 server on the network. I'm happy to share the config. I don't know where NM stores the config information received, it's got to be there, somewhere.

Well, show me what you have. 

dresden:~ # egrep -v '^#|^$' /etc/dhcpd6.conf authoritative; default-lease-time 86400; preferred-lifetime 43200; option dhcp-renewal-time 3600; option dhcp-rebinding-time 7200; allow leasequery; ddns-updates on; ddns-update-style interim; ddns-domainname "local.net."; use-host-decl-names on; update-static-leases on; update-conflict-detection false; log-facility local2; option dhcp6.name-servers 2a03:7520:4c68:1::1000; option dhcp6.info-refresh-time 21600; option dhcp6.macaddr code 193 = string; option dhcp6.leased-address code 194 = string; option dhcp6.macaddr = binary-to-ascii(16, 8, ":", suffix(option dhcp6.client-id, 6)); option dhcp6.leased-address = binary-to-ascii(16,16, ":", substring(suffix(option dhcp6.ia-na, 24),0,16)); shared-network enidan { subnet6 2a03:7520:4c68:1::/64 { ddns-rev-domainname "1.0.0.0.8.6.c.4.0.2.5.7.3.0.a.2.ip6.arpa"; #ddns-domainname "local.enidan.com"; # if we don't know the host, we create our own name. if not exists host-name { log (info, concat ("Lease for ",leased-address, " leased to ", config-option dhcp6.macaddr)); ddns-hostname = concat( "dynip-", binary-to-ascii( 10, 8, "-", suffix( leased-address, 2 ))); } pool6 { deny unknown-clients; range6 2a03:7520:4c68:1:ff99::/112; } pool6 { allow unknown-clients; range6 2a03:7520:4c68:1:ff99:ffff::/112; } } } zone local.net { primary localhost; } zone 1.0.0.0.8.6.c.4.0.2.5.7.3.0.a.2.ip6.arpa { primary localhost; } [All host entries deleted.]

However, I think I will file a bug report.  This shouldn't be so difficult for something that's supposed to be automatic.

My setup is 10 years old (judging by the changelog entries), but as I mentioned, ISTR some issue with the RDNSS option. I needed to use dhcpv6 anyway, as I want to assign hostnames that way. I only use NM on laptops, but that should not matter. Of course I use ipv6 for a gazillion android devices too. -- Per Jessen, Zürich (14.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.

James Knott wrote:

On 2022-09-26 15:18, Per Jessen wrote:

...

dresden:~ # egrep -v '^#|^$' /etc/dhcpd6.conf

authoritative; default-lease-time 86400; preferred-lifetime 43200; option dhcp-renewal-time 3600; option dhcp-rebinding-time 7200; allow leasequery; ddns-updates on; ddns-update-style interim; ddns-domainname "local.net."; use-host-decl-names on; update-static-leases on; update-conflict-detection false; log-facility local2; option dhcp6.name-servers 2a03:7520:4c68:1::1000; option dhcp6.info-refresh-time 21600; option dhcp6.macaddr code 193 = string; option dhcp6.leased-address code 194 = string; option dhcp6.macaddr = binary-to-ascii(16, 8, ":", suffix(option dhcp6.client-id, 6)); option dhcp6.leased-address = binary-to-ascii(16,16, ":", substring(suffix(option dhcp6.ia-na, 24),0,16));

Again, that's the server, which is not where the problem is. 

Hmm, I suggest it is a server side issue. I use a different dhcp server and for me it works, albeit on Leap 15.2. AFAICT, there is no client side config to share, but if you know where it is, I'll be happy to post mine.

I can capture the DHCPv6 packets and see the DNS info.  It just doesn't get used, as far as I can tell.  Also, my DHCPv6 server is on pfsense, which runs on FreeBSD. The problem is on 15.4 and only when using network manager.

I have not yet moved to 15.4, except on some virtual machines. Can't really help with that. -- Per Jessen, Zürich (14.4°C)

On 2022-09-26 09:00:12 James Knott wrote:

|On 2022-09-26 09:11, Patrick Shanahan wrote: |> there is configuration available in NetworkManager and you may assign |> the servers*you* desire. why not configure it instead of filing a bug |> report. | |The point is this is supposed to work and doesn't.  As mentioned, this |is on a notebook computer, which can be moved to different locations.  |At home, I want to use my own DNS server, as it contains local addresses |that are useless elsewhere.  That DNS would not be available to me |elsewhere.  Saying to manually configure something that's supposed to |work automatically isn't a solution.  It works with Windows and Android, |but not Leap 15.4.  Also, this problem has been around for a while with |SLAAC and RDNSS.  I have only recently been able to try it with DHCPv6.  |So, that's two methods that should work, but don't.

There are some settings in YaST => Sysconfig Editor => Other => etc =>sysconfig => network => config & dhcp that might help with this? Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 x86_64