whats the frequency of the letter * in:
q: nginx - server change - redirect all traffic to new ip address? i want to change the server of a website and usually the way of doing it, is this:

*

*check the ttl of the domain which points to the current ip address.

*change the a-record of the the current domain to point to the new ip address.

but in this case there are still requests, that will point to the current ip address until all nameservers understood the change.
how can i prevent that? is the nginx reverse proxy the right tool to direct all traffic to the new ip address? and if so, do i just need to do it this way on the current server and thats it?
location ~ \ {
    proxy_pass http://newipaddress:8000;
}

thanks!

a: the reverse proxy is the perfect tool for this kind of change for a number of reasons. here are a few:

*

*as you mentioned some name servers will provide the old ip address to the clients, so some clients will request the old server

*with dns change you would need a new public ip address or at least change your nat configuration on your corporate firewall

*in the case there are failures on the new server switching back takes more time due to ttl

so to sum it up: changing the backend ip on the nginx minimizes changes on the corporate firewall and gives you the possibility to switch very quickly.
configuration as you mentioned is just:
location ~ \ {
   proxy_pass http://newipaddress:8000;
}

site note: alternatively you could write the ip addresses of your backend server and a fitting hostname in your /etc/hosts file and mention this hostname in your proxy_pass directive. this has the advantage that in case of switching servers you just would need to change the entry in /etc/hosts instead of changing multiple configuration files.

user
In that passage, there are 7 occurrences of the letter "*."
assistant