allow changing DNS when using DHCP

  • When i use DHCP and then try to change the DNS it says its forbidden, which is a bit odd. Unfortunately, in my country we are sometimes forced to use a different DNS server than the one that is sent by the proprietary router (where nothing like dns is configurable).

  • Go to Best Answer
  • Code
    connmanctl config <service_name> --nameservers 8.8.8.8 1.1.1.1

    The GUI is probably coded around the concept of mutually exclusive DHCP or Manual connection. See if you can set it from the CLI?

  • i can set it from cli, yes, but cli is not an option for "regular" users. i can do that for myself, but when my little sis asks me "how can i do that?" (because she gets blocked because or her ISP), then she has 0 chance to change anything thats not changable from UI.

    There are RFCs out there that mention that DHCP DNS settings must not be forced and user overrides should be accepted (something like that...), so imo this would be a reasonable and nice feature

  • i can set it from cli, yes, but cli is not an option for "regular" users. i can do that for myself, but when my little sis asks me "how can i do that?" (because she gets blocked because or her ISP), then she has 0 chance to change anything thats not changeable from UI.

    Skeeve
    October 26, 2025 at 6:49 PM
  • When i use DHCP and then try to change the DNS it says its forbidden, which is a bit odd. Unfortunately, in my country we are sometimes forced to use a different DNS server than the one that is sent by the proprietary router (where nothing like dns is configurable).

    Hi, Do you strictly need to use DHCP at that device? I'm thinking about, you could to start to configure the network with DHCP. After it's connected, change to "manual". The values obtained by DHCP will remain, and you change only the parameters that you want (DNS server). Maybe worth a try...

  • feels like a joke to me somehow... so its blocked because its blocked, which makes no sense at all to me - even the rfc for dhcp states dns should be overwritable by the user - the only thing thats blocking is the UI, for no reason at all, just because it can be blocked? therefore people that are not familiar with networking but must use a different dns are doomed when they dont know how to configure their network with cli or manually... or not to use libreelec at all. i got it. i give up.


    VLouis thanks, thats a workaround that might probably work. but i am wondering why this workaround is required at all. but guess i dont understand this "we must block manual dns overwrites because we can" mentality.

  • The LE settings add-on has long history of "if it works, don't fix it" style maintenance because it's all Python code that nobody on current project staff understands; and in that context you'll argue "but it doesn't work" and I'd argue it does for 99.9999% of our users and Dr. Spock's logic quote "the needs of the many outweigh the needs of the few" applies. There's also a general desire to keep interfaces simple and supporting all possible configuration options generally adds complication.

    That said, the codebase is all GPLv2 and open-source so there is nothing to stop someone submitting the technical changes that implement the feature you desire. It's just unlikely to be someone on staff as we have learned to avoid that Python juju.