[MDEV-9207] Spurious error warning on IP Resolve Created: 2015-11-29 Updated: 2022-09-08 |
|
| Status: | Confirmed |
| Project: | MariaDB Server |
| Component/s: | OTHER |
| Affects Version/s: | 5.5, 10.0, 10.1 |
| Fix Version/s: | 10.1 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Guillaume Lefranc | Assignee: | Sergei Golubchik |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
151129 17:38:09 [Warning] IP address '104.197.125.66' has been resolved to the host name '66.125.197.104.bc.googleusercontent.com', which resembles IPv4-address itself. Google cloud resolves all its internal addresses like the above, so thousands of warnings are generated in the error log. IMHO the warning is not really useful and the detection is too sensitive in the following function: static inline bool is_hostname_valid(const char *hostname) The above affirmation complies to RFC952, but is obsoleted by RFC1123. RFC1123 specifies the following: The syntax of a legal Internet host name was specified in RFC-952 Suggestion: make the above referenced function RFC1123 compliant. |
| Comments |
| Comment by Elena Stepanova [ 2015-11-29 ] |
|
I've set the fix version to 10.0/10.1 thinking it does not seem to be dangerous to suppress the warning even in a post-GA release, but please adjust as needed. |
| Comment by DEZILLIUM LIMITED [ 2016-10-22 ] |
|
Can we bump the priority for this bug up a bit? Logs are flooded with warnings on servers having multiple clients connecting to them. Log flooding might seem like a nuisance to some, but each line takes processing time and space to be logged. Logs filling up a server's disk isn't that unheard of, which is generally regarded as SHTF (S*** Hitting The Fan). For argument's sake: |