Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-26 Thread Michael Catanzaro
On Fri, Mar 26 2021 at 01:24:35 PM -0400, przemek klosowski via devel wrote: As to the issues with F5, I see that it rewrites /etc/hosts You can ask them to fix their software according to my instructions here:

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-26 Thread przemek klosowski via devel
I've been having problems with DNS resolution in F33 as well: I use F5 VPN (work requirement). I tried your nsswitch recipe, but got some errors: authselect apply-changes [error] [/etc/nsswitch.conf] is not a symbolic link! [error] [/etc/nsswitch.conf] was not created by authselect!

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-26 Thread Zbigniew Jędrzejewski-Szmek
On Thu, Mar 25, 2021 at 09:54:11AM -0500, Michael Catanzaro wrote: > On Thu, Mar 25 2021 at 09:26:19 AM -0500, Michael Catanzaro > wrote: > >For now, keep nss-myhostname at the start of the line, right after > >files. We will probably need to find a way to either (a) fix > >systemd-resolved to

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-25 Thread Michael Catanzaro
On Thu, Mar 25 2021 at 09:26:19 AM -0500, Michael Catanzaro wrote: For now, keep nss-myhostname at the start of the line, right after files. We will probably need to find a way to either (a) fix systemd-resolved to handle mDNS properly, so we can move it after nss-resolve, where it really

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-25 Thread Robert Marcano via devel
On 3/25/21 10:21 AM, Michael Catanzaro wrote: On Thu, Mar 25 2021 at 08:37:03 AM -0400, Robert Marcano via devel wrote: IMHO the fedora name should be always resolvable the same way as localhost or just remove it. It is not right thsat fedora is being resolved only while the DHCP server

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-25 Thread Jerry James
On Wed, Mar 24, 2021 at 7:51 PM Robert Marcano via devel wrote: > Maybe changing the default hostname to fedora wasn't a good idea after > all, or at least fedora should be added to the default /etc/hosts. Note that setting the hostname to "fedora" also led to log spam, for me at least:

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-25 Thread Michael Catanzaro
On Thu, Mar 25 2021 at 09:26:19 AM -0500, Michael Catanzaro wrote: We spent a long time thinking about the order the NSS modules should be listed, but then made a last-minute change to move nss-mdns4_minimal forward in order to work around a bug with systemd-resolved not handling mDNS

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-25 Thread Michael Catanzaro
OK, so then the problem here is avahi, or more specifically, that nss-mdns4_minimal is listed before nss-resolve and nss-myhostname. We need nss-myhostname to come before nss-mdns4_minimal. Drat. We spent a long time thinking about the order the NSS modules should be listed, but then made a

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-25 Thread Michael Catanzaro
On Thu, Mar 25 2021 at 08:37:03 AM -0400, Robert Marcano via devel wrote: IMHO the fedora name should be always resolvable the same way as localhost or just remove it. It is not right thsat fedora is being resolved only while the DHCP server isn't assigning you a new hostname. You never

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-25 Thread Robert Marcano via devel
On 3/24/21 9:51 PM, Robert Marcano wrote: Currently I am connecting to a VPN that provides a few DNS search entries. One of these domains on the search path is having DNS resolution problems. This is not per se the the problem I am  writing this email for. The problem is that starting

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-25 Thread Robert Marcano via devel
On 3/25/21 7:30 AM, Petr Menšík wrote: Hi, I would guess your domainname is not (none), and hostname -f value is fedora.domain_failing.tld. One of fixes might be to change hostname of the machine to not contain domains suffix. Then only explicitly configured search would apply. No: #

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-25 Thread Robert Marcano via devel
On 3/24/21 11:26 PM, Michael Catanzaro wrote: Hi, I have a couple different ideas of what could be going wrong. Let's test a few things. First, please run: $ cat /etc/nsswitch.conf | grep hosts | tail -1 If it is our default configuration, it should say: hosts: files mdns4_minimal

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-25 Thread Petr Menšík
Hi, I would guess your domainname is not (none), and hostname -f value is fedora.domain_failing.tld. One of fixes might be to change hostname of the machine to not contain domains suffix. Then only explicitly configured search would apply. On 3/25/21 2:51 AM, Robert Marcano via devel wrote: >

Re: Default 'fedora' hostname and failing split DNS VPN

2021-03-24 Thread Michael Catanzaro
Hi, I have a couple different ideas of what could be going wrong. Let's test a few things. First, please run: $ cat /etc/nsswitch.conf | grep hosts | tail -1 If it is our default configuration, it should say: hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return]

Default 'fedora' hostname and failing split DNS VPN

2021-03-24 Thread Robert Marcano via devel
Currently I am connecting to a VPN that provides a few DNS search entries. One of these domains on the search path is having DNS resolution problems. This is not per se the the problem I am writing this email for. The problem is that starting Firefox and Thunderbird take a long time, it