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.If the ping and traceroute test show your server with us in the outcome, you know the DNS is propagated. You can try speeding up the propagation time by having your TTL set to a lower number (not recommended). We set the default TTL to 14400 (4 hours); however the network that you are using to access the internet may update at a slower rate.However, in many cases when the DHCP and DNS configurations have inconsistencies, the LDNS may direct the DHCP client to a place outside the local scope, resulting in leakage of private DNS updates to the global network.In the example shown above, the LDNS is not configured with a local zone for 168.192.``So what if my host leaks a few packets to the global Internet? '' The reason is that inconsistent configuration between your home hosts and your local DNS servers can, and often does, cause leakage of DNS updates for private IP addresses to the global Internet.
Most home users who use DSL/Cable routers as DHCP/NAT servers to facilitate multiple host connections to the Internet should turn off dynamic DNS updates.When you make a DNS change, it takes time for the changes to take effect. It is the time it takes for the domain DNS to refresh the cache on the network.The cache is cleared over a certain amount of time.The following list illustrates a typical example of how a private DNS update leaks out to the global Internet. The DHCP client first sends a query to its local domain name server (LDNS) and asks for the authoritative server for the zone of its domain name (step 3).Once the DHCP client receives a response (step 4), it sends the update to the indicated server (step 5).