Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, February 13, 2014 3:07 PM
Hello,
we are using static DNS records on our company's router and Windows is not trying to resolve hostnames.
For example on the router is set DNS foo for address 192.168.2.1
When I try ping foo from linux machine, it works just fine. But it is not working on Windows, because windows doesn't even try to resolve this kind of "short" hostnames.
It works when it's changed to foo.foo or when foo is added into hosts file. But adding it on every machine is what I don't want to do.
Is there a way how to configure Windows to resolve these short hostnames via DNS ?
Thanks
All replies (4)
Thursday, February 13, 2014 3:16 PM ✅Answered
Does windos use Router as its dns server. You might have to configure network connection settings to add .foo as dns suffix
Can you post the result of nslookup and
nslookup
set type=ns
any hostname
Thursday, February 13, 2014 3:25 PM ✅Answered
Please see Ace Fekay's response in this thread, particularly around the DNS suffix topic:
If that's not close enough to the mark, or there are added complexities in your environment just let me know.
Thursday, February 13, 2014 7:48 PM
Thanks for your response.
Yes, windows is using router as it's only dns server. It works fine with longer hostnames (hostname has to have at least two parts). I'll try the other stuff tomorow. I'm already outside the network.
This guy has exactly the same problem, maybe he is explaining it better. Problem is that windows don't even give it a try to resolve the name through dns. Everything works fine from Linux systems.
Wednesday, February 19, 2014 8:21 AM
Hi,
Have the issue persists if you add the DNS suffix in TCP/IP settings?
If you need further assistance, please feel free to let us know.
Best regards,
Susie