I'm getting random DNS-releated failures on my app server connecting to the mysql instance. Everything runs fine for a little while, then suddenly int-mysql-master.analytics.<mydomain>.com can't be found.
If I run dig int-mysql-master.analytics.<mydomain>.com on the app server, I get no "response" section. The authority section shows <mydomain>.com. If I run dig @ns1.scalr.net int-mysql-master.analytics.<mydomain>.com and force a lookup on scalr's primary DNS server, it returns a positive response and shows the right authority: analytics.<mydomain>.com. What's very strange is it does work sometimes. I can get about 10 http requests through the app server, it connects to the mysql instance just fine and displays data. The app server was also able to run setup scripts on the mysql instance. When things break, it lasts a few minutes then starts working again for a few requests. When failures occur on the app server, running the same dig command on a different machine returns valid results. Also, the app server connects successfully to the mysql instance when using IP addresses, so I know the issue is not related to the mysql role. I have zero idea where to go from here. It looks to me like DNS requests sent from the app server get matched against <mydomain>.com rather than the analytics.<mydomain>.com zone and therefore can't find a match. But I'm not a DNS expert, so I might be missing something. Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
