I think I might have found the issue here. As with Michael Flaig (the bug reporter) it's a local network without a gateway (it is set as 0.0.0.0 so it won't give you internet access obviously). When I set a fake gateway the resolv.conf file is updated!
Question arises: Is it by design that nameservers of IPv4 configs without a gateway will not be passed to resolvconf (or NM will not write it to the resolv.conf file)?
This is behaviour I didn't expect and is quite different than in Hardy and previous releases. I would assume that this bug or design brakes lots of network configurations.
I think I might have found the issue here. As with Michael Flaig (the bug reporter) it's a local network without a gateway (it is set as 0.0.0.0 so it won't give you internet access obviously). When I set a fake gateway the resolv.conf file is updated!
Question arises: Is it by design that nameservers of IPv4 configs without a gateway will not be passed to resolvconf (or NM will not write it to the resolv.conf file)?
This is behaviour I didn't expect and is quite different than in Hardy and previous releases. I would assume that this bug or design brakes lots of network configurations.