I thought this might be the problem.
Open Terminal
Issue this command "sudo pico /etc/hosts"
Enter an administrative password
You'll see something like quoted below
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
Use your arrow keys to get below the lowest listing
Type in the static IP address for the server, computer, device you are wanting to create a manual entry for
Hit tab
Type in the hostname (example: automation engine)
You should see something like this:
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
192.168.3.99 automationengine
Hold the control key and strike the X key
Save modified buffer (ANSWERING "No" WILL DESTROY CHANGES) ?
strike the Y key
hit Enter/Return
You're now back to the standard terminal prompt. You'll want to verify your entry.
type: ping automationengine
hit Enter/Return
If you see this you are good to go:
chevaliers-macbook-pro:~ che$ ping automationengine
PING automationengine (192.168.3.175): 56 data bytes
64 bytes from 192.168.3.99: icmp_seq=0 ttl=128 time=0.355 ms
Hold the control key and strike the C key to make it stop.
Close the terminal (type: exit, apple+Q, file>quit, whatever)
If you see this something is wrong:
chevaliers-macbook-pro:~ che$ ping automationengine
ping: cannot resolve automationengine: Unknown host
Restart the computer (not always necessary)
Open Terminal
type: ping automationengine
hit Enter/Return
If you are still not working go back to the first step and verify you have not entered any typos and your spelling is absolutely perfect.
TIP (not always necessary): enter the hostname in as many capital letter configurations as you can think of with a tab between each. Sometimes this behavior is case-sensitive. Example:
1.1.1.1 automationengine AUTOMATIONENGINE AutomationEngine AUTOMATIONengine automationENGINE
I've yet to find a real solution to this. Manual DNS entries is a duct-tape patch not a real solution. At scale (imagine a environment with more than 5 OSX sdevices) this would a nightmare hence why DNS is handled by servers… Windows2003 DNS servers had a check box you could force clients to accept updates but with Windows2008 this disappeared. The whole issue boils down to how OSX computers update and cache DNS. This quirk affects all kinds of things (including prepress software from other vendors) when a Windows server is providing DNS.