4 ms·
I don't understand the root cause... Did nobody at Fiserv know about example.com or the .invalid TLD? I see this sort of thing ALL the time - documentation ref
by ancarda 6y ago
I don't understand the root cause... Did nobody at Fiserv know about example.com or the .invalid TLD?
I see this sort of thing ALL the time - documentation referring to completely made up domains like "newcustomer.com", and it soon makes its way into software becoming real world DNS lookups for these placeholder domains. Nobody ever goes back and changes them and there's no monitoring or awareness that it's an issue.
Please take a moment to read BCP 32 - https://tools.ietf.org/html/bcp32 https://tools.ietf.org/html/bcp32 if you do not know about example.com or the .invalid TLD.
- JdeBP 6y agoI can envisage the explanation of the root cause. "example.com." is seen as for examples in documentation, and what is the case here appears, rather, to be placeholder values in softwares that have not been fully installed and configured with the correct information for the company. This might not be the case, but it seems likely. And yes, the "invalid." top-level domain might have been suitable, although one might equally question the wisdom of an application that is sending mail (rather than complaining loudly) when its mail settings have not yet been configured.
- mro_name 6y agoisn't a placeholder a certain case of an example?