Are the DNS well set par dhcp ?

Is /etc/resolv.conf saying something ?

For example I have :
-------------
# Generated by NetworkManager
search home mars.bidon
nameserver 192.168.1.1
nameserver 2a01:cb04:152:8f00:aa6a:bbff:fe77:adf0

It says:
; cat /etc/resolv.conf
# Generated by NetworkManager
search login.stonet.cc doma.org
nameserver 192.168.11.1
;

Thanks.
R

... and at this moment I have no idea where that login.stonet.cc comes from...
(Though, it probably does not relate to my main problem.)
R

After experimenting with my /etc/resolv.conf I, eventually, see
something. I have removed the 'search' line completely (that should
not matter, moreover, I do not understand where the 'login.stonet.cc'
comes from). Next, I was changing the nameserver from the one mentioned
above to 8.8.8.8, and back, a few times. Quite consistently, with
the original 192.168.11.1 I am unable to get to either office365 or
Teams, while I can connect to them with 8.8.8.8 . I do not understand why,
but it behaves so (as it seems).

Surprisingly, it's the 192.168.11.1 that other Windows machines use,
and that works for them.

I do not know what to think about it.

Thanks.

Ruda

I wouldn't rule the "search" line out so quickly.

Looking at `man resolv.conf`, I think that a quick way to test if it plays a role is to set the LOCALDOMAIN variable

I would try the following: First close ALL instances of firefox already running. Then launch firefox from a terminal with:

and then attempt to login to Office365

Oh I didn't see your last post when I wrote mine :-)

So I guess the "search" line doesn't matter and the issue is with the DNS server in your Wifi router at 192.168.11.1 (except if you have your own DNS server in your LAN)

There must be some slight differences in the DNS requests during the O365 login on Linux, Windows and OpenBSD and that's enough to trip your router DNS server... DNS is a beast!


Using Google (8.8.8.8) is a good solution.

Also, /etc/resolv.conf is generated by NetworkManager. In the Network Manager Applet (if you use one for example in KDE) you could add dns entries for this network. An so try 8.8.8.8 without manually change resolv.conf

Did you try to change the DNS without touching the search line ?

You can also add the DNS entries of your internet provider (the real ones and not the one of the box).

You may want to dig further with dig(1). Assuming office365.com is the problem url, you can compare the output of:

$ dig @192.168.11.1 office365.com
$ dig @8.8.8.8 office365.com
$ dig @[your isp DNS server IP] office365.com