MWEB Business clients' massive data loss

[herbertk]

Bit of a blanket statement here. Depends entirely on the situation. Many developers don't have control over their client's DNS so it can be preferable to use an IP if they are liable to update it, let it expire, etc. Obviously generally less maintenance to use a FQDN but an IP can be updated immediately without waiting for DNS to propagate when time is of the essence. Also when the application is first rolled out clients sometimes haven't worked out their domain name, etc. Calling developers rubbish if they happen to use an IP address for something without knowing the situation is uncalled for.

+1 for instance some firewalls cannot use DNS for rules so the access rules has to be done on IP, so even if there was DNS changing the IP would cause issues.

 

[The_Unbeliever]

Using hardcoded (or softcoded) IP's instead of FQDN's is just downright silly and stupid.

 

[Sinbad]

+1 for instance some firewalls cannot use DNS for rules so the access rules has to be done on IP, so even if there was DNS changing the IP would cause issues.

Firewall = single point of control. Thousands of deployed clients is not. Your argument is invalid.

 

[FatBoySlim]

Firewall = single point of control. Thousands of deployed clients is not. Your argument is invalid.

Well the ip address is hardcoded into the mobile app, with Android its a blessing in which case an update can be deployed within minutes.
Apple, totally different story with a review process taking upto a week.

 

[Valerion]

One advantage of using IP addresses is that you're immune to DNS Spoofing / cache poisoning attacks. If you are allocated a long-term static IP address I don't see a reason not to use it. Obviously not for a user-accessible website, but in a config file you can easily replace it should be fine (e.g. OpenVPN).