Bug #54369 | Connecting from 10.10.x.x network issues. | ||
---|---|---|---|
Submitted: | 9 Jun 2010 14:34 | Modified: | 12 Aug 2010 6:10 |
Reporter: | Rolf Martin-Hoster | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: General | Severity: | S1 (Critical) |
Version: | 5.1.46 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | connecting, Connections, dns, IP, private, reverse |
[9 Jun 2010 14:34]
Rolf Martin-Hoster
[9 Jun 2010 14:35]
Rolf Martin-Hoster
I should add that this was discovered after we went live and was preventing us from getting replication going.
[10 Jun 2010 7:50]
Sveta Smirnova
Thank you for the report. What does recolveip ADDRESS print?
[10 Jul 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[10 Jul 2010 23:57]
Rolf Martin-Hoster
The proper 10.10.x.x address. The problem is that reverse dns is not always appropriate for private networks. It would be nice if you could check the hosts file as well if no reverse is found.
[12 Jul 2010 6:10]
Sveta Smirnova
Thank you for the feedback. If resolveip returns correct IP address you should be able to connect. Please send us command you use to connect to MySQL server and error message you get. You also mentioned "new DOS protection". Does it mean you changed something in your application or do you mean particular change in MySQL code?
[12 Aug 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".