I'm running Debian 12.1 using Vagrant on HyperV and connecting to a network using a virtual switch.
If I try to access resources on the public internet it works fine, but it fails to resolve resources on my local domain.
The DHCP lease seems correct from `/var/lib/dhcp/dhclient.eth0.leases`172.23.224.1 is the address for the virtual switch and also the DHCP/DNS server
If I manually specify a DNS server; then name resolution succeedsBut it fails if I don't.
Resolvconf is runningAnd the contents of `/etc/resolv.conf` isI'm pretty sure that I've got an issue with how resolv is configured but don't know how to proceed from here
Any help is appreciated.
If I try to access resources on the public internet it works fine, but it fails to resolve resources on my local domain.
The DHCP lease seems correct from `/var/lib/dhcp/dhclient.eth0.leases`
Code:
default-duid "\000\001\000\001,\240\017\004\000\025]\012\016\307";lease { interface "eth0"; fixed-address 172.23.230.141; option subnet-mask 255.255.240.0; option dhcp-lease-time 86400; option routers 172.23.224.1; option dhcp-message-type 5; option domain-name-servers 172.23.224.1; option dhcp-server-identifier 172.23.224.1; option dhcp-renewal-time 43200; option dhcp-rebinding-time 64800; option domain-name "mshome.net"; option netbios-node-type 4; renew 4 2025/01/09 23:34:54; rebind 4 2025/01/09 23:34:54; expire 4 2025/01/09 23:34:54;}lease { interface "eth0"; fixed-address 172.23.230.141; option subnet-mask 255.255.240.0; option dhcp-lease-time 86400; option routers 172.23.224.1; option dhcp-message-type 5; option domain-name-servers 172.23.224.1; option dhcp-server-identifier 172.23.224.1; option dhcp-renewal-time 43200; option dhcp-rebinding-time 64800; option domain-name "mshome.net"; option netbios-node-type 4; renew 5 2025/01/10 09:06:34; rebind 5 2025/01/10 17:34:57; expire 5 2025/01/10 23:34:57;}
If I manually specify a DNS server; then name resolution succeeds
Code:
nslookup my.domain.local 172.23.224.1
Resolvconf is running
Code:
● resolvconf.service - Nameserver information manager Loaded: loaded (/lib/systemd/system/resolvconf.service; enabled; preset: enabled) Active: active (exited) since Fri 2025-01-10 00:47:55 UTC; 8min ago Docs: man:resolvconf(8) Process: 2569 ExecStart=/sbin/resolvconf --enable-updates (code=exited, status=0/SUCCESS) Main PID: 2569 (code=exited, status=0/SUCCESS) CPU: 1msJan 10 00:47:55 debian systemd[1]: Started resolvconf.service - Nameserver information manager.
Code:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN# 127.0.0.53 is the systemd-resolved stub resolver.# run "resolvectl status" to see details about the actual nameservers.nameserver 4.2.2.1nameserver 4.2.2.2nameserver 208.67.220.220search mshome.net
Any help is appreciated.
Statistics: Posted by Chronocide0 — 2025-01-10 01:02 — Replies 2 — Views 79