Besides the relative difficulties in getting the subdomain added (hostX does not have a do-it-yourself domain manager panel), is there a performance issue in how this gets set up? In particular, I'm guessing that my rails app on HostingRails will have much higher traffic than the corporate web site at www.thecompany.com. e.g., Should or could I use HostingRails DNS for both the domain and subdomain? Or does it come to simply which is easiest to do?
DNS servers, subdomains, and performance
- Fredder
- Posts: 15
- Starts: 8
- Wiki Edits: 0
I'm setting up a new application on HostingRails that will be pointed to by a subdomain. E.g. myrailsapp.thecompany.com. I wasn't involved in the original set up, but the domain name was registered through Active-domain.com, and when the corporate web site (www.thecompany.com) was hosted (e.g., 'hostX'), the DNS server for the domain was changed to the hostX server from the default Active-domain provided DNS servers.
Besides the relative difficulties in getting the subdomain added (hostX does not have a do-it-yourself domain manager panel), is there a performance issue in how this gets set up? In particular, I'm guessing that my rails app on HostingRails will have much higher traffic than the corporate web site at www.thecompany.com. e.g., Should or could I use HostingRails DNS for both the domain and subdomain? Or does it come to simply which is easiest to do?
Besides the relative difficulties in getting the subdomain added (hostX does not have a do-it-yourself domain manager panel), is there a performance issue in how this gets set up? In particular, I'm guessing that my rails app on HostingRails will have much higher traffic than the corporate web site at www.thecompany.com. e.g., Should or could I use HostingRails DNS for both the domain and subdomain? Or does it come to simply which is easiest to do?
- William
- Posts: 1010
- Starts: 32
- Wiki Edits: 56
Its probably better to keep control over your own DNS - if you are able to set an A record for your domains to point to any IPs you want then this is usually best. Just point myrailsapp.thecompany.com to the IP of your account (shared or dedicated) and it will work. There shouldn't be any performance issues, as long as you have your nameservers set to grab zone files from seperate boxes (i.e. a primary and secondary nameserver) then there will rarely be DNS timeouts.
2007-04-12 02:24 PM
- Nick
- Posts: 2
- Starts: 1
- Wiki Edits: 0
I'm looking to do something similar to Fredder, where for now, at least, only a subdomain will be hosted at HostingRails. The problem I seem to be hitting is that from HR's servers, the DNS entries seem to want to map my whole domain (e.g. .company.com) rather than just myrailsapp.company.com. This prevents me from accessing my svn server, databases, or other resources at other subdomains of company.com.
Am I able to re-map what piece of my domain is hosted at hostingrails through the cpanel somewhere? I'm a brand new hostingrails customer, so I'm just not familiar with too much about the admin interface yet. I didn't see anything obvious, though.
Thanks.
Am I able to re-map what piece of my domain is hosted at hostingrails through the cpanel somewhere? I'm a brand new hostingrails customer, so I'm just not familiar with too much about the admin interface yet. I didn't see anything obvious, though.
Thanks.
2007-04-13 10:40 AM
- William
-
- Posts: 1010
- Starts: 32
- Wiki Edits: 56
Again - if you're hosting your main domain and other subdomains elsewhere - then you shouldn't be pointing your domain's nameservers at us. You only need to point an A record for the subdomain to your IP. Does that make sense? You can use your servername.hostingrails.com or your IP to connect to your svn, databases, and other resources.... let me know if I need to clarify. Cheers, ~William
2007-04-13 10:50 AM
- Nick
-
- Posts: 2
- Starts: 1
- Wiki Edits: 0
What you're saying makes sense. However, if I run: nslookup www.mydomain.com from the shell at hostingrails, I get a different result than I do if I run it from my home machines or other domains. In other words, I believe HostingRails is defaulting to mapping the whole domain name which I typed in when I signed up, and so hostingrails machines are getting the wrong DNS entries.
2007-04-13 11:15 AM
- Kumar
- Posts: 423
- Starts: 0
- Wiki Edits: 5
Hello Nick,
Please note that when a domain is created on our servers, it also creates a DNS entry for your domain on our servers with default nameservers set by us. So the nslookup on the server will only show the our server IP as DNS will be resolved locally on our servers first instead of resolving the domain from outside. You may please email support so that we can make the changes to the DNS db file which we have on our servers to have external nameservers or we can kill the DNS entry on our server since you don't require to use our nameservers
~Kumar
Please note that when a domain is created on our servers, it also creates a DNS entry for your domain on our servers with default nameservers set by us. So the nslookup on the server will only show the our server IP as DNS will be resolved locally on our servers first instead of resolving the domain from outside. You may please email support so that we can make the changes to the DNS db file which we have on our servers to have external nameservers or we can kill the DNS entry on our server since you don't require to use our nameservers
~Kumar
2007-04-13 12:13 PM
HostingRails Support- William
-
- Posts: 1010
- Starts: 32
- Wiki Edits: 56
Right - in other words, if a zone file gets created on our nameservers, this means nothing to the outside world unless you point your domain's nameservers to them.
2007-04-13 01:12 PM
- Micktaiwan
- Posts: 4
- Starts: 2
- Wiki Edits: 0
- Location: Toulouse, France
I have created subdomains, but it seems that sometimes their are not propagated to other DNS. If use nslookup or dig and asking to resolve the name directly using hostingrails dns, it always work. But living in France, it seems that the name is not always propagated. Some days it work, some other not.
Is it completely related to my France DNS, or did you have any feedback on this issue ?
Is it completely related to my France DNS, or did you have any feedback on this issue ?
2008-07-03 12:56 PM
- Rahul
- Posts: 474
- Starts: 0
- Wiki Edits: 1
Hello,
In your particular case, Can you make sure that you are using the following NameServers..
=
ns10.hostingrails.com
ns1.hostingrails.com
=
If there is any trace of 'ns2.hostingrails.com' related with your domain.. Then please do remove the entry from the registrar end and make sure that ns10 and ns1 are the primary Name Servers of the domain name associated with these sub-domains.
We had closed down the 'ns2' nameserver some time back.. So do check and confirm the status from your end.
In your particular case, Can you make sure that you are using the following NameServers..
=
ns10.hostingrails.com
ns1.hostingrails.com
=
If there is any trace of 'ns2.hostingrails.com' related with your domain.. Then please do remove the entry from the registrar end and make sure that ns10 and ns1 are the primary Name Servers of the domain name associated with these sub-domains.
We had closed down the 'ns2' nameserver some time back.. So do check and confirm the status from your end.
2008-07-03 03:36 PM
Regards,Rahul