How to deal with dynamic IP address in MS Access to MYSQL DB Maria (2 Viewers)

[nector]

Good afternoon, all!

See how you can advise when using MYSQL DB Maria ODBC connector. Connecting to the DB require composing an ODBC string like below:

ODBC;DRIVER={MySQL ODBC 8.0 ANSI Driver};UID=nectorcomza_nector;USER=nectorcom_nectororgza;SERVER=102.216.81.111;PORT=3306;PASSWORD={XXXXXXXXXXXXXX};NO_SCHEMA=1;DFLT_BIGINT_BIND_STR=1;DB=nectorcomza_Accounts;DATABASE=XXXXXXXXXXXXXX;FILEDSN=XXXXXXXXXXX:\Us

So far so good no issues in connection from MS Access and the speed is excellent, it's like you are using a local MS Access DB:

Problem Area:

The router public IP address changes every day or in short, its dynamic all our six stations it's like that, for us to connect the users we keep on recapturing the new IP addresses on phpMyAdmin. For example, if the new public IP address is 102.116.80.111 then we have to enter like this 102.116.80. %, but the problem the change might be a different number like 41.160.87.116

The implication here is that as long as the new public IP address is not captured on phpMyAdmin then no one will manage to connect to the DB meaning everyday you have to be changing. Is there a solution to this ?

 

[cheekybuddha]

You may need to investigate a service like dyndns.org

 

[sonic8]

You may need to investigate a service like dyndns.org

I doubt this will help.
The problem is not the hostname of the server, but the IP addresses of the clients used for restricting access to the MySql server to known hosts only, - Is this correct, @nector ?
Even when using dynamic DNS services like DYN (formerly DynDNS), a reverse DNS lookup of the IP address will still resolve to the original hostname, e.g. something like "host123456.region.provider.com", and is as dynamic as is the IP address.