Hi,
Probably... I think you cannot dig hosts inside your scalr server
because of the record for your zone had not added to the file
'named.conf'.
I've recently had the same problem. I suppose that's a bug.
You need to add the following into your 'named.conf':
zone "sample.tm.local" {
type master;
file "pri/sample.tm.local.db";
};
At least, I've done it exactly so. Maybe, in new version of scalr it
has been fixed.
I'm going to upgrade RC2 to RC3, but not now... I don't have time :(
If you'll be trying to do that, please let us know the result.
Good luck,
Nick.
On 17 дек, 09:03, cocoy <[email protected]> wrote:
> I've configured scalr on ec2 and installed bind. When I launch a farm,
> with mysql and app server it runs ok. My internal domain is tm.local
> w/ ns1.tm.local set as nameserver.
>
> An application was created as sample.tm.local. And created the zone
> file:
>
> @ 14400 IN SOA server1.tm.local. root.server1.tm.local. (
> 2008121702 ; serial, todays date+todays
> 14400 ; refresh, seconds
> 7200 ; retry, seconds
> 86400 ; expire, seconds
> 300 ) ; minimum, seconds
>
> sample.tm.local. 14400 IN NS server1.tm.local.
> ext-app 20 IN A 10.252.66.147
> int-app 20 IN A 10.252.66.147
> @ 90 IN A 10.252.66.176
> ext-mysql 20 IN A 10.252.66.176
> ext-mysql-master 20 IN A 10.252.66.176
> int-mysql 20 IN A 10.252.66.176
> int-mysql-master 20 IN A 10.252.66.176
>
> Unfortunately I cannot dig these hosts inside scalr server(but
> ns1.tm.local is ok).
> Can you advice what's wrong with the setup?
>
> Thanks in advance,
> Rodney
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
