Not sure as to how to flush the dns in the astaro. A reboot of the box should do the job.
It may be that the computers on the network are resolving using the arp table so its worth clearing them to. - ipconfig /flushdns
One way to see if its the astaro firewall resolving the address is to change one of the clients DNS server settings to another dns then see if nslookup resolves to the address.
I am unable to reproduce this on the ASG. What I did: - created a Static DNS mapping "test -> 1.1.1.1" - "ping test" from ASG, test resolves to 1.1.1.1 - delete the mapping - "ping test" from ASG, "ping: unknown host test"
Are you sure, that the problem is not the dns cache of your workstation?
I am positive. I tried multiple machines. Multiple OS's. Rebooting machines. I tested as you did from the ASG and it knew how to resolve it. I flushed the dns. Tried everything except the reboot. Finally rebooted and all was well.
on the ASG itself, the static entries will go out of scope immediately after deleting them. However they are created with a TTL of one day, so they may stick in downstream resolvers for up to 24 hours. This may include all kinds of caches (Browser, workstation, AD DNS, whatever).
We'll lower the TTL for static entries to just 60 seconds. However this is not a bug [:)]
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
