Sorry, my previous message had inaccurate info. I was actually using subdomain IN A 174.XXX.XXX.XX
...which unfortunately is still not working. Any other ideas? It seems like changing the DNS settings in scalr simply aren't adding the appropriate A or CNAME records to DNS. On Jan 22, 4:56 am, Matt McGinnis <[email protected]> wrote: > The problem could be that a dot is required at the end of the record > if you are using the full domain name. If you just use the subdomain, > you don't need the dot. Both of the following are valid: > > subdomain.domain.com. IN A 174.XXX.XXX.XX > > OR > > subdomain IN A 174.XXX.XXX.XX > > On Jan 21, 8:03 pm, Mike Lee <[email protected]> wrote: > > > Hi, > > > I am trying to point a subdomain to one of the instances in my farm. > > I have tried both of the following methods: > > > - adding a CNAME record to point to the external name of the instance, > > i.e. ext-base.domain.com. > > > - using an elastic IP for the instance, and creating an A record for > > the subdomain which points to that IP, i.e. > > > subdomain.domain.com IN A 174.XXX.XXX.XX > > > However, after making those changes to the default DNS settings for my > > application, the subdomain still does not resolve. > > > How do I setup a subdomain to point to one of the instances in my > > farm? > > > Any help would be greatly appreciated. > > > Mike --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
