Dns host record not updating
This enabled people to refer to other computers by the name, and their computer translated that name to an IP address when it needed to communicate with it. It comes with all Windows machines The location for the hosts file is normally C\windows\system32\drivers\etc As network sizes increased the hosts file approach became impractical due to the fact that: The hosts file is simply a list of names and IP addresses with no structure making it difficult to scale to a large number of machines.
The solution is to place the machines into administrative areas known as domains, and arrange the domains in a hierarchy.
A host can be used to maps hostnames associated with malware to a different IP address (such as a loopback address, 127.0.0.1).
This will prevent connections to those malicious sites from ever taking place.
(There is an irony here, as some of the more “evil” malware hijacks your host file to prevent their removal or to redirect search queries).
Unfortunately, there are several problems with using host files, especially in a corporate environment: As an alternative to host files, there are several desktop-based DNS software packages available which are designed for use on a single desktop.
Visual Domain Routing Tool You can also ping and trace route your domain locally from your Windows/Mac command prompt to verify what IP you are actually seeing.
The DNS system is nitpicky to work with, and the DNS setup for your domain affects important business activities, like email!
When you add your domain to Office 365, typically your domain's MX record is updated (by you or Office 365) to point to Office 365, and ALL email sent to that domain will start coming to Office 365.
You can take steps to pilot Office 365 with just a few email addresses instead.
There are a couple of scenarios when you just need to verify your organization's domain and not set up any services.