Unusual DNS issue affecting your local network.
Unusual DNS issue affecting your local network.
I employ tools such as synergy to manage a single mouse and keyboard on both PC and Mac, along with network devices like WDMyCloud and a home server. Recently, I've faced several DNS issues that aren't coming from my router. For instance, accessing 1.1.1.1 or Google's 8.8.8.8 works fine, but opening \\wdmycloud only via direct IP causes significant slowdowns. On my Windows home server or PC, setting the 192.168.1.1 DNS from the router resolves everything again. This also affects my ability to locate other Synergy machines and causes further complications. My question is whether it's feasible to use one DNS server for a specific network range like 192.168.1.0/24 while employing different DNS servers globally on all devices.
You shouldn't notice speed differences between these tasks except for the time it takes your router to connect WDmycloud to its IP address. The problem could stem from using a static DNS on your device instead of your router. Your router would recognize your personal DNS server, which might not match WDmycloud's independent DNS server. Using its correct IP should remove the need for nslookup, but the router might still interfere causing delays. Regarding your request, there’s no software that differentiates LAN from WAN requests and applies the right DNS automatically. It seems unnecessary to route through your router for DNS purposes. Consider setting your router to use your preferred DNS or standardize across devices. This should fix the issue unless your ISP is redirecting traffic.
It's unusual. I refreshed Synergy now and it's functioning properly, but WDMyCloud seems to be facing issues. Perhaps a setting on the router is causing this. I'll also review my Cloud settings in case I discover something useful there.
You should specify the DNS forwarders in the router to be 1.1.1.1 or 8.8.8.8, not your local DNS values on network interfaces on PC's etc on the network. DNS on local systems should look at the DNS resolver on the router, the DNS resolver on the router should then provide internally known DNS A records via itself. Any unknown (External) requests should then be passed via the external forwarders. Looks like this; / External > External Forwarder > External DNS Server (e.g 1.1.1.1) > DNS Record located Local PC >> DNSLookup >> Router >> Local or External \ Local > Routers DNS resolver > Internal DNS Record located If using 1.1.1.1 or 8.8.8.8 is a requirement you have on local PC's, you will need to add local DNS values to the HOSTS file to bring in a bypass to force DNS resolution.
According to @Falconevo, all devices like computers, NAS, or printers should connect to your Router/Firewall for DNS. Then, configure the router/firewall to use any external settings you prefer.
Thanks everyone, I've verified the issue clearly. The computer attempts to reach the DNS server on the network card when resolving names. Using 1.1.1.1 and 8.8.8.8 shows it's trying to connect to the local IP 169.254.73.158, which isn't found. Ethernet 6 reports another host at 169.254.3.124 linked to cloudflare-dns.com. Everyone is correct. A minor issue: my router blocks DNS changes, and I'm using a NOS Hitron router in Portugal. My connection speed is 200Mbps with their provider, but I can't modify the firmware or change DNS settings. It seems I might be facing LAN conflicts or being restricted to their DNS. Possible reasons include pirated sites being blocked.
He shared that he recently purchased an expensive Asus router and is using the same ISP to send traffic through it. He says the router likely connects to a DMZ or similar setup using two good gigabit cables, and everything is managed from there. It’s not a bad solution, but I’m hesitant to spend over 200€ just for a DNS issue. For now, I’ll keep this approach until someone has a better idea.