- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
This is a challenging problem All applications should be using DNS but we know this isn't always the case. The DNS process is entirely handled on the client, converting the DNS name to an IP. There is no way to check this for a simple file server. This check is possible on a web server - is your file server a web server?
Thinking about solutions, you can always just rip off the bandaid and move the server and update DNS. If you launch an awareness campaign through your IT Organization with published deadlines and an active support campaign post move - you should be good. If you want to do a little more work, you can setup the file server in AWS, replicate the content and setup the old IP address with a proxy to the new server. This way you will be able to see which clients didn't follow the DNS update.
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa