Petit souci depuis la mise en place de mon serveur DNS.
Le resolv.conf retourne ceci :
[root@heracles ~]# cat /etc/resolv.conf
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0 trust-ad
search xxxx.xxx lan
configuration du réseau
$ sudo nmcli device show enp34s0
[sudo] Mot de passe de xxxxxx :
GENERAL.DEVICE: enpXXs0
GENERAL.TYPE: ethernet
GENERAL.HWADDR: XX:XX:XX:B6:11:CB
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connecté)
GENERAL.CONNECTION: enp34s0
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.CARRIER: marche
IP4.ADDRESS[1]: 192.168.1.XX/24
IP4.GATEWAY: 192.168.1.XXX
IP4.ROUTE[1]: dst = 0.0.0.0/0, nh = 192.168.1.XXX, mt = 100
IP4.ROUTE[2]: dst = 192.168.1.0/24, nh = 0.0.0.0, mt = 100
IP4.DNS[1]: 192.168.1.XXX
IP4.DNS[2]: 192.168.1.XX
IP4.DOMAIN[1]: lan
IP6.ADDRESS[1]: fe80::XXx:XXxx:xxxX:XXxx/64
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 100
Comme je sais que l'on a changé de gestionnaire de DNS (utilisation de systemd-resolve), je ne sais pas si il faut utiliser un programme ou faire des modifications à la main dans les fichiers de conf?
C'est un peu pénible, car de base on gère cela avec networkmanager, mais cela ne semble pas être pris en compte...
Normalement FreeIPA-client gère cela, mais même constat, cela ne semble plus être pris en compte 🙁