Try using host int-mysql.yourdomain
On 11.12.08 20:56, "ken" <ken.ever...@gmail.com> wrote: > > Hi Alex, > I was using nslookup to compare. I've cut/paste the terminal session > info below. > > From my production apache server: > dep...@ec2-67-202-63-15:~$ /sbin/ifconfig -a > inet addr:10.249.71.79 > > dep...@ec2-67-202-63-15:~$ nslookup int-mysql > Server: 172.16.0.23 > Address: 172.16.0.23#53 > > From my staging apache server: > dep...@ec2-174-129-133-31:~$ /sbin/ifconfig -a > inet addr:10.249.75.130 > > dep...@ec2-174-129-133-31:~$ nslookup int-mysql > Server: 172.16.0.23 > Address: 172.16.0.23#53 > > ~K > > On Dec 11, 12:07 am, Alex Kovalyov <alex.koval...@gmail.com> wrote: >> IPs appear to be different for me in your zones. >> Please make a screenshot and mark the overlapping records if possible. >> >> On 11 дек, 03:16, ken <ken.ever...@gmail.com> wrote: >> >>> Hi Sclar team, >> >>> We've got a production and staging farm running nicely using your >>> service. Very slick stuff. >>> Looking around at DNS configured by our application, I noticed that >>> the internal DNS overlaps. >> >>> Farm 817 (production) and Farm 962 (staging) >> >>> This results in some very similar dynamically generated internal DNS. >>> For example, they both know "int-mysql" and they resolve to the same >>> IP on both. If we begin wiring our farms together using internal >>> DNS, that could be trouble. >> >>> Are we approaching this correctly? Seems the internal DNS should be >>> different. >>> ~Ken > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to scalr-discuss@googlegroups.com To unsubscribe from this group, send email to scalr-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
