Windows domain - name resolution issues from Mac OS X 10.9
I have an odd issue that is a recent occurrence. However, I'm not sure exactly how recent, and so trying to find any event log entries is difficult.
I have an SBS 2008 server running as a Hyper-V guest on a Windows 2012 host. The SBS 2008 server was converted from a physical server. It's IP address was 192.168.1.100/24. Since being converted to Hyper-V (over a year ago), it also has the IP 192.168.1.32/24. The Server 2012 has an IP of 192.168.1.101/24. I also have a NAS unit on 192.168.1.200/24
I used to be able to ping my Hyper-V server and NAS unit using their NetBIOS names from my MacBook Pro (OS X 10.9 Mavericks). However, now when I try and ping, I get the following error:-
ping: cannot resolve <name>: Unknown host
If, however, I use nslookup from my Mac, then the names resolve with the FQDN (i.e. name.mydomain.local). I can also ping the FQDN.
What I want to do though, is go back to being able to ping the NetBIOS name only.
How do I do this?
I have an SBS 2008 server running as a Hyper-V guest on a Windows 2012 host. The SBS 2008 server was converted from a physical server. It's IP address was 192.168.1.100/24. Since being converted to Hyper-V (over a year ago), it also has the IP 192.168.1.32/24. The Server 2012 has an IP of 192.168.1.101/24. I also have a NAS unit on 192.168.1.200/24
I used to be able to ping my Hyper-V server and NAS unit using their NetBIOS names from my MacBook Pro (OS X 10.9 Mavericks). However, now when I try and ping, I get the following error:-
ping: cannot resolve <name>: Unknown host
If, however, I use nslookup from my Mac, then the names resolve with the FQDN (i.e. name.mydomain.local). I can also ping the FQDN.
What I want to do though, is go back to being able to ping the NetBIOS name only.
How do I do this?
ASKER
@PeterLbk - from what I understand, the Bonjour service uses the .local suffix when there is only one label in addition to .local (i.e. server.local) - but when there are two or more additional labels (i.e. server.mydomain.local) then name resolution takes place using a regular DNS server.
On my Mac, DNS resolution has worked for well over a year on my SBS network - it's only been over the last couple of weeks that the resolution has stopped working.
On my Mac, DNS resolution has worked for well over a year on my SBS network - it's only been over the last couple of weeks that the resolution has stopped working.
Did you check the dns table of the server? I know windows has a strange way of supplying dns records... do you have the right records, both forward and reverse? No double records either?
NetBIOS is Windows only/mainly. If you want to ping the name, you should put an alias in DNS. nslookup queries the Domain Server directly. ping and dig get it from your local system's DNS cache. It may need to be reloaded.
You could flush you DNS cache to try and force a reload to fix it.
Lion & newer
sudo killall -HUP mDNSResponder
Leopard
sudo dscacheutil -flushcache
Tiger
lookupd -flushcache
Windows
ipconfig /flushdns
http://etherealmind.com/flush-dns-cache-on-mac-os-x/
You could flush you DNS cache to try and force a reload to fix it.
Lion & newer
sudo killall -HUP mDNSResponder
Leopard
sudo dscacheutil -flushcache
Tiger
lookupd -flushcache
Windows
ipconfig /flushdns
http://etherealmind.com/flush-dns-cache-on-mac-os-x/
ASKER
@PeterLbk - DNS on Windows Server has the correct forward and reverse lookup zones configured and has been working for ages. Although it's an SBS setup, I'm running it in a home environment and no other machines have been added to the network.
@serialband - For over a year, I have been able to browse internal websites using the host name only (without the domain.local suffix), and I've been able to ping host names. As it stands, I cannot ping by hostname only and yet nslookups work ok.
@serialband - For over a year, I have been able to browse internal websites using the host name only (without the domain.local suffix), and I've been able to ping host names. As it stands, I cannot ping by hostname only and yet nslookups work ok.
Maybe your DNS cache became corrupt today. Try clearing it. I've had that happen before.
ASKER
I've already done this on the Mac AND on the Windows Server....
what happens if you try and add dns of your windows server to your mac and then try to PING it ?
ASKER
My Mac is getting an IP from the SBS DHCP Server, and when I check the DNS settings in the system preferences, I can see that the 2 expected DNS addresses are assigned (and in the correct order) and that the search domain mydomain.local is also assigned.
I am running out of options :)
Try to create a new test user account on a mac and see if it works from that account.
do you have any other mac to test it from. if yes, what happens if you test, does it work.
Have you recently installed any updates etc ?
Try to create a new test user account on a mac and see if it works from that account.
do you have any other mac to test it from. if yes, what happens if you test, does it work.
Have you recently installed any updates etc ?
ASKER
I will try another account. I only have the one Mac - however, there are 2 iPhones, an iPad and an iPod touch all on the same network, all which resolve OK.
There have been no Mac or Windows updates installed prior to this happening...
There have been no Mac or Windows updates installed prior to this happening...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
nice one
ASKER
any .local name will be used in a multicast lookup and won't be checked by dns.