3 ms·

I'm currently on Ubuntu 18.04 and I love it but: - Firefox takes literally 10 seconds to start unless I disable eth0 - Chromium isn't able to resolve DNS for

I'm currently on Ubuntu 18.04 and I love it but: - Firefox takes literally 10 seconds to start unless I disable eth0 - Chromium isn't able to resolve DNS for local intranet sites - Have not tried chrome as installing it means fiddling with apt repos, wget or gdebi These issues are unresolved as of January 2019. I can't say that I ever had such issues on macOS. I have had DNS issues because of my specific ISP router after a major macOS upgrade but my ISP patched it within a week.

cheald 8y ago
The first two issues both sound like you have misconfigured DNS and the first resolver in your list is invalid (and has to time out). The same misconfiguration under OSX would be likely to create the same issues.
- systemtest 8y ago
  Thank you for solving the first issue! I switched DNS from automatic to manual. Now I do have to adjust this every time I switch networks so perhaps I should write a script that does this automatically.
  - dpark 8y ago
    Why are you manually configuring DNS? If you need it to switch between different networks, it sounds like you should let DHCP do its job instead of overriding it.
  - kilburn 8y ago
    If your problem is over wifi, NetworkManager (the default in Ubuntu) should let you do this automatically. Networkmanager defines a "connection" for every (stored) wifi, which you can view: nmcli connection show Now, you can set the dns servers to use when any of these connections is activated. For instance, define google's servers by: nmcli conn mod <connection-name> ipv4.dns "8.8.8.8 8.8.4.4" This will override the DNS settings (which come from DHCP by default) whenever you connect to this specific network :)
    - base698 8y ago
      This never works for me... can't ever get it to stick, tried all kinds of ways to mod with nmcli or systemctl restart/reload network manager. Debating on just doing a cron job to rewrite resolv.conf.
      - Tsiklon 8y ago
        In the server environment at least, Ubuntu 18.04 makes use of `systemd-resolve`, running a dns server locally. Have you looked at setting DNS with that?
      - kilburn 8y ago
        I'm not an ubuntu user (debian testing here). I remember that various systemd-thingies were actually tweaking some network settings behind NetworkManager's back. Getting NetworkManager to work properly was a matter of disabling all that systemd stuff and then setting it up using config files and nmcli (the gnome GUI just broke everything too easily). My impression after all that was that NetworkManager is a very capable piece of software littered with bad interfaces and impenetrable documentation. You will emerge victorious if you fight those hard enough. In contrast, trying to setup the system using the various systemd-thingies got me to "xxx is planned but not working now" every time. Btw, I do have a weird complicated network configuration because I'm switching between ethernet and wifi, and have multiple bridged and/or routed vms/containers (with all of kvm, lxc, and virtualbox).

cheald 8y ago

The first two issues both sound like you have misconfigured DNS and the first resolver in your list is invalid (and has to time out). The same misconfiguration under OSX would be likely to create the same issues.

systemtest 8y ago
Thank you for solving the first issue! I switched DNS from automatic to manual. Now I do have to adjust this every time I switch networks so perhaps I should write a script that does this automatically.
- dpark 8y ago
  Why are you manually configuring DNS? If you need it to switch between different networks, it sounds like you should let DHCP do its job instead of overriding it.
- kilburn 8y ago
  If your problem is over wifi, NetworkManager (the default in Ubuntu) should let you do this automatically. Networkmanager defines a "connection" for every (stored) wifi, which you can view: nmcli connection show Now, you can set the dns servers to use when any of these connections is activated. For instance, define google's servers by: nmcli conn mod <connection-name> ipv4.dns "8.8.8.8 8.8.4.4" This will override the DNS settings (which come from DHCP by default) whenever you connect to this specific network :)
  - base698 8y ago
    This never works for me... can't ever get it to stick, tried all kinds of ways to mod with nmcli or systemctl restart/reload network manager. Debating on just doing a cron job to rewrite resolv.conf.
    - Tsiklon 8y ago
      In the server environment at least, Ubuntu 18.04 makes use of `systemd-resolve`, running a dns server locally. Have you looked at setting DNS with that?
    - kilburn 8y ago
      I'm not an ubuntu user (debian testing here). I remember that various systemd-thingies were actually tweaking some network settings behind NetworkManager's back. Getting NetworkManager to work properly was a matter of disabling all that systemd stuff and then setting it up using config files and nmcli (the gnome GUI just broke everything too easily). My impression after all that was that NetworkManager is a very capable piece of software littered with bad interfaces and impenetrable documentation. You will emerge victorious if you fight those hard enough. In contrast, trying to setup the system using the various systemd-thingies got me to "xxx is planned but not working now" every time. Btw, I do have a weird complicated network configuration because I'm switching between ethernet and wifi, and have multiple bridged and/or routed vms/containers (with all of kvm, lxc, and virtualbox).