Hi Martin,

Most likely, it cached a negative response for this particular subdomain.

Is this still happens for you? If so, please give the farm id and I'll check it.

Nick

2009/7/8 MartinB <[email protected]>:
>
> How come 172.16.0.23 resolve mydomain.com, but not int-mysql-
> master.mydomain.com ?!
>
> This prevent my app from working correctly!
>
> On Jul 8, 7:26 am, Nickolas Toursky <[email protected]> wrote:
>> Hi Martin,
>>
>> 172.16.0.23 is the EC2 internal DNS server. It caches both successful
>> and negative (NXDOMAIN) responses.
>> ns1.scalr.net as well as ns2.scalr.net are non-recursive name servers.
>> You cannot use them to resolve arbitrary domains.
>>
>> Nick
>>
>> 2009/7/7 MartinB <[email protected]>:
>>
>>
>>
>> > Hi,
>>
>> > I changed the dns for my domain earlier today and it seems to be
>> > working fine except that locally in my EC2 instance, it won't resolv
>> > the subdomain like int-mysql.domain.com
>>
>> > So I figured the EC2 server wasn't using a DNS that was updated so I
>> > looked around and found /etc/resolv.conf which has something like:
>>
>> > search compute-1.internal
>> > nameserver 172.16.0.23
>>
>> > So what is that IP? Looks  like it's not even to Amazon?
>> > I replaced it with the IP of ns1.scalr.net for now and that partly
>> > fixed my problem. I mean the site now works and can connect to int-
>> > mysql.domain.com since it now resolves, but it seems that
>> > ns1.scalr.net won't resolve my SVN domain.
>>
>> > I guess my questions are
>>
>> > 1- Will DNS 172.16.0.23 catch up within 48 hours?
>> > 2- Why isn't ns1.scalr.net resolving another domain?
>>
>> > 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to