MX23 DNS problem

[altreed]

Hi,

I am new to linux.

I have installed MX23 and have a windows server homelab lan.

My problem is the MX receives dhcp from my windows server that nominates the local dns, but when I try to contact other windows machines using their dns names e.g delllap.c-i.local , MX cannot contact them but all the windows network is working fine. If I use the IP of the windows machine rather than the dns name then MX can communicate, but I do not understand why it is not using the dns server to resolve.

I have been searching the interweb and there lots of suggestions, but nothing seems to work or make any difference.

Thanks

Code: Select all

System:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=<filter> ro quiet splash
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.1_KDE_x64 Libretto
    October 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: Micro-Star model: PRO Z690-A (MS-7D25) v: 2.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: A.80 date: 08/31/2022
CPU:
  Info: model: 12th Gen Intel Core i5-12600K bits: 64 type: MST AMCP arch: Alder Lake gen: core 12
    level: v3 note: check built: 2021+ process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151)
    stepping: 2 microcode: 0x32
  Topology: cpus: 1x cores: 10 mt: 6 tpc: 2 st: 4 threads: 16 smt: enabled cache: L1: 864 KiB
    desc: d-4x32 KiB, 6x48 KiB; i-6x32 KiB, 4x64 KiB L2: 9.5 MiB desc: 6x1.2 MiB, 1x2 MiB L3: 20 MiB
    desc: 1x20 MiB
  Speed (MHz): avg: 800 high: 801 min/max: 800/4900:3600 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 801 7: 800 8: 800 9: 800 10: 800
    11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 bogomips: 117964
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW
    sequence
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel AlderLake-S GT1 vendor: Micro-Star MSI driver: i915 v: kernel ports: active: none
    empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2, HDMI-A-3, HDMI-A-4 bus-ID: 00:02.0 chip-ID: 8086:4680
    class-ID: 0380
  Device-2: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX] driver: amdgpu v: kernel arch: RDNA-3
    code: Navi-3x process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: DP-3 empty: DP-4,DP-5,HDMI-A-5 bus-ID: 03:00.0 chip-ID: 1002:744c class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: amdgpu,modesetting unloaded: fbdev,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 3440x1440 s-dpi: 96 s-size: 910x381mm (35.83x15.00") s-diag: 987mm (38.84")
  Monitor-1: DP-3 mapped: DisplayPort-2 model: AOC U34G3G3R3 serial: <filter> built: 2022
    res: 3440x1440 hz: 165 dpi: 110 gamma: 1.2 size: 797x334mm (31.38x13.15") diag: 864mm (34")
    modes: max: 3440x1440 min: 720x400
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon Graphics (gfx1100 LLVM 15.0.6
    DRM 3.49 6.1.0-13-amd64) direct-render: Yes
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: AMD driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 03:00.1 chip-ID: 1002:ab30 class-ID: 0403
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I225-V vendor: Micro-Star MSI driver: igc v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0a:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: lxcbr0 state: down mac: <filter>
Drives:
  Local Storage: total: 9.45 TiB used: 51.84 GiB (0.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Samsung model: SSD 960 EVO 250GB size: 232.89 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 3B7QCXE7 temp: 18.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:8 vendor: Seagate model: XPG GAMMIX S70 size: 1.86 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 3.2.7.3 temp: 61.9 C scheme: MBR
  ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Seagate model: FireCuda 530 ZP4000GM30013
    size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: SU6SM003 temp: 26.9 C scheme: GPT
  ID-4: /dev/sda maj-min: 8:0 vendor: Corsair model: Force 3 SSD size: 83.85 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 5.02 scheme: GPT
  ID-5: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000DM006-2G5107 size: 3.64 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: DN04 scheme: GPT
Partition:
  ID-1: / raw-size: 83.59 GiB size: 81.73 GiB (97.77%) used: 51.84 GiB (63.4%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 275 KiB (0.1%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 6 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 27.0 C mobo: N/A gpu: amdgpu temp: 66.0 C mem: 85.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 681
Repos:
  Packages: 2553 pm: dpkg pkgs: 2526 libs: 1391 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 27
  No active apt repos in: /etc/apt/sources.list
  No active apt repos in: /etc/apt/sources.list.d/amdgpu-proprietary.list
  Active apt repos in: /etc/apt/sources.list.d/amdgpu.list
    1: deb https://repo.radeon.com/amdgpu/5.5.3/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm main non-free
    2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/rocm.list
    1: deb [arch=amd64] https://repo.radeon.com/rocm/apt/5.5.3 focal main
  Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
    1: deb [arch=amd64] https://repo.skype.com/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/waydroid.list
    1: deb [signed-by=/usr/share/keyrings/waydroid.gpg] https://repo.waydro.id/ bookworm main
Info:
  Processes: 386 Uptime: 12h 14m wakeups: 2 Memory: 31.13 GiB used: 6.91 GiB (22.2%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

[j2mcgreg]

@altreed
Welcome to MX.
Your biggest challenge is going to be unlearning the Microsoft Windows way,
The answer to your question is fairly simple. Your MX desktop expects to be redirected to your Windows server by your router and your router uses its list of internal ip addresses to do so. DNS is an internet facing protocol and in Linux is not used internally on a LAN.

[bassplayer69]

What you can do in the interim is configure your hosts file with those machines.

[CharlesV]

There are a number of services that can help with this, but try pinging the windows machine with a .local on the end of the windows machine name.
like this

winbox.local

And if the machines are static you can add to your hosts file as bassplayer mentioned.

[FullScale4Me]

In KDEs Settings ---> System Settings ---> Network ---> Connections ---> Wired Connection 1 select the IPv4 tab.

In the field "Other DNS Servers:" enter the Ip Address of your Router and click apply. If your router is picking up your ISPs targeted DNS servers you should have them working on the next reboot.

The Avahi client on MX *may* be able to resolve them, as machine.local *if* you open your MX 23's Uncomplicated Firewall to the mDNS port of 5353 UDP (1). See MX Linux 23 User Manual section 4.5.1

1) use Preconfigured rule: "PLEX Avahi discovery" More https://fullscale4me.com/uncomplicated-firewall.pdf

[altreed]

Hi,

Thanks for the suggestions.

I have a slightly more complex setup than std home user. I have a windows router onto a DMZ to the fibre router. So all my dhcp and networking is in a M$ bubble. I need my mx to recieve dhcp and dns settings to connect to the local machines/VM's.

I have tried using full domain names when trying to connect to the windows machines, but mx can't resolve the machine IP. Suggests it is just not using the dns settings issued with the dhcp. I will try a fixed IP config pointing IP settings, see if that makes any difference.

Thanks
D

[FullScale4Me]

I've got 15+ years IT Ops Support experience in at several Big Pharmas. My concept of complex is NOT the same as yours I am sure of.

There was one Pharma that had a DMZ room the size of a large studio apartment. Just the fibre bundle alone entering the building was the size of an adult forearm. Copper was bigger.

[DukeComposed]

I have tried using full domain names when trying to connect to the windows machines, but mx can't resolve the machine IP. Suggests it is just not using the dns settings issued with the dhcp. I will try a fixed IP config pointing IP settings, see if that makes any difference.

You can verify what DNS resolvers the MX machine is using by checking the contents of /etc/resolv.conf and seeing if they match the nameservers that are suggested by your DHCP server.

[FullScale4Me]

Good point DukeComposed.

Complex environments sometimes get seemingly meaningless configuration changes applied. Seen a few in my day that slept and didn't break anything until a time or so later. Hard to trace as reverting recent changes gives no joy!

A thought I had was firewall/router blocking broadcast name resolution. Not clear if the OP's install of MX has it in Broadcast or Hybrid mode. Example: Avahi uses broadcast to ask other Avahi clients about unknown hosts. They reply directly on port 5353 UDP.

Common Firewall Port usage

* Avahi 5353 UDP a mDNS (aka Bonjour) provider - use Pre-configured rule: "PLEX Avahi discovery".

* DHCP UDP port 67 on the server side.
UDP port 68 on the client side. Pre-configured rule adds port 67 only.

* DNS 53 TCP & UDP

* = Use the "Pre-configured" application rule for these common devices in the GUFW app.

[altreed]

You can verify what DNS resolvers the MX machine is using by checking the contents of /etc/resolv.conf and seeing if they match the nameservers that are suggested by your DHCP server.

Thanks for a helpful comment.

I checked the resolve.conf and this is what it said :-

"nameserver 25.25.25.1
nameserver 8.8.8.8"

My dhcp/dns/AD is on 25.25.25.1 obvs 2nd dns is google.com or somewhere, which is part of the dhcp settings. So the dhcp part has worked as intended it seems. However, the mx does not seem to resolve local machines at the local dns server. I have tried FQDN and variations on that with suggestions above. But it resolutely doesn't seem to work as all my windows machines that just work without hiccup, many are workgroup machines using dhcp rather than domain registered machines.

It seems odd, almost silly, but annoying!

I am considering rebuilding my machine with a larger NVME boot storage which a fresh mx will be loaded, then I will put a dual boot windows on my other nvme. Maybe this will overcome the silly dns issue.

I just had put a next next next mx install on my build, so I have no idea what facilities had been installed. I only wanted a basic install and taste of Linux. I have tried other flavours of linux over the years, liking mx the most.

I started my IT career in 1986 working at a nuclear experiment site/network, so yes I do know what complex can look like. I have since managed an active directory windows network since 1995 growing to over 700 workstations. My comment was only that I do not simply have a wireless network at home with 3 laptops and a broadband/cable router.

Thankyou for your help.