Name resolution in my local network doesn't work any more.
Hi, today the name resolution in my local network stopped working. The windows explorer brings the error 0x80070035. This happens on all device, using the ip works, not using any host names.
PS C:\Windows\system32> nslookup wintermute
Server: dns2.nextdns.io
Address: ---
Nicht autorisierende Antwort:
Name: wintermute.fritz.box
Addresses: ---
45.76.93.104 << should that be a local 192.168.xxx.xx ip address from my network ?
8 replies
-
If you have your own DNS server, see https://github.com/nextdns/nextdns/wiki/Split-Horizon
if you have a small number of local hosts you can se the rewrites option under the Settings tab on my.nextdns.io
-
Thank you for your answer.
"If you have your own DNS server, see https://github.com/nextdns/nextdns/wiki/Split-Horizon"
I only use nextDNS directly in my router (AVM Fritzbox 7530 AX).
"if you have a small number of local hosts you can se the rewrites option under the Settings tab on my.nextdns.io"
I'll try that.
-
"if you have a small number of local hosts you can se the rewrites option under the Settings tab on my.nextdns.io"
Can i really use the hostnames or do i need to use hostname.local for that?
Do i need to flush the dns cache on my device and reboot the router for that?
-
Can i really use the hostnames or do i need to use hostname.local for that?
Use whatever the host is actually named. Is it wintermute.fritz.box ?
You can flush cache or wait for TTL to expire
-
No, i use the standard hostnames without domain. wintermute as example.
-
those look correct to me. I have similar entries and they’re working as expected. Perhaps your network settings are using a default domain of fritz.box Try resolving but placing a dot at the end of your query.
nslookup wintermute.lan. <——the dot on the end might helpWithout the dot, your system might try to append fritz.box to your query. Somewhere in windows settings might be a “default domain” which is getting automatically appended to your queries.
-
-
This is maybe not a NextDNS issue, since someone (not AVM) recently bought the fitz.box domain?
(Apologies if German is not your native language; it’s not mine either, but I couldn’t find an English article about this)
Content aside
-
1
Likes
- 8 mths agoLast active
- 8Replies
- 248Views
-
3
Following