I'm in the use case where I had nothing on this domain, nothing was started on either side, I just bought the domain on the wrong service.
I imagine it's possible to transfer ownership to AWS, so that I may start managing the DNS from there rather than from dreamhost.
I probably could have purchased the domain from route 53 in the first place but this is now done and I don't want for the year under dreamhost to time out to start using it. nor do I want to use dreamhost to manage this url since dreamhost charges quite a lot more.
I've found the amazon guide that's my exact situation, but as per ususal with these guides they're super afraid of providing a concrete example and get into super abstracts with reused terminology for different meaning resulting in an unusable jumble of uncertainties : https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-inactive.html
So I've gotten to :
Step 3: Create records (inactive domains)
I've just manually edited the values that were created by default by route 53 when I created that hosted zone to the ones I found in the dreamhost DNS configuration :
but I doubt that's what I have to do to transfer the domain especially since the step after that basically sais to change it back to what it was.
So what is it exactly I'm supposed to do in order to transfer the domain to amazon (route 53)?
Domain registration and DNS resolution are related, but separate entities. It seems like you decided you want route53 to serve your DNS entries. Given that, you have two choices.
Choice 1: Keep domain registered with dreamhost
If you do this, you need to instruct dreamhost to look up DNS entries for your domain at route53. This can be accomplished by setting the NS servers on dreamhost to point to route53. There are detailed instructions for this at AWS here. What you have in your step3 is backwards. Step 3 is just saying if you want HOST.yourdomain.com, to add a entry 'HOST' into the hosted zone. You should not touch the NS or SOA entries on the route53 hosted zone away from their original settings. You can simply delete the zone and start over again.
Background: Dreamhost will populate the NS entries by default and they will be the ones queried how to resolve HOST.yourdomain.com. However, if you don't provide dreamhost any information that they should refer the requests to route53, it has no way of knowing that. You need to tell dreamhost that the NS entries (Nameserver) should point to route53's servers. That way, the user trying to resolve HOST.yourdomain.com will be pointed to route53. When it asks route53 what the IP is, all will be well if you setup your hosted zone to resolve that entry. This is what you are going to do on step 4 from the AWS documentation.
Choice 2: Transfer your domain registration to route53
This is a little more up front work, but may be easier in the long run. You are permitted to transfer the domain to another domain registrar. You'll have to follow instructions at both the giving side (dreamhost) and the gaining side (route53).
NOTE: ICANN does enforce a 60 day lock on moves. If you just registered your domain, you will need to wait 60 days before the transfer process can begin. Also, do not worry about 'double paying' for the year. You are required to purchase at least one more year of domain registration, but it will be appended to the end date of your expiration (it won't start it over). Once you move to route53, especially if you already are using route53 for the hosted zone, you will have one less place to pay and administer.
Additional NOTE: Because of the 60 day lock, if it has been less than 60 days since you created the domain, choice #1 is the only choice during that period if you want to serve DNS records from route53.
Related
I have a dedicated server centos 6.4 with plesk 12. I created to my existing domain.com an subdomain media.mydomain.com to move store there the images.
I created the subdomain also on provider side (3days ago). I also create an A Record on cloud flare point to my static servers ip (2 days ago). When I enter yet, media.mydomain.com to the browser, I get just a blank page, nothing more. When I check the DNS for my subdomain then i get the following message:
Delegation not found at parent.
No delegation could be found at the parent, making your zone unreachable from the Internet.
Not enough name server information was found to test the zone media.mydomain.com, but an IP address lookup succeeded in spite of that.
I don't know, how i can get my subdomain working, can someone give me tip, how i can accomplish that?
A blank page in your browser actually sounds like a server issue not delivering content. Difficult to look at without knowing the actual subdomain in question.
On github I have made the CNAME record of my domain name. My domain is registered with crazy domains. I went to crazy domains and entered the ip address for the name server, "204.232.175.78". But it keeps asking for a "hostname". It will not allow me to leave the hostname area blank. In the past I have been told to use a hostname like "ns1.host.com" but I can't seem to find anything like this for github pages.
I tried "pages.github.com" but it refuses that, saying it is not a valid hostname.
What should I use as the hostname?
I believe the issue is that you're updating your nameserver registration, when in fact you should be editing your DNS Zone File. Those are two separate records. The nameserver registration determines who's copy of the DNS Zone File acts as master on the domain. The DNS Zone File is what actually controls A, CNAME, MX, and SRV records (and many more). You should try looking through your domain management system (I'm not familiar with Crazy Domains) to see if you can find a section called "All Host Records" or "DNS Zone Editor".
F#$k crazy domains. They changed their interface to try to get everyone to upgrade to premium. On the hamburger on the right side of DNS settings you can add a record there (not forward) and then the CNAME stuff appears.
Seriously considering changing because of this.
I am hosting a service on Windows Azure and using an external DNS (Gandi) to manage zone files. What I would like is to redirect all the incoming Azure traffic to another web page, while I am updating the service (like we'll be back soon).
I know that I can do this by updating the zone file, but it takes time to propagate, then time to put back into normal. So 1 hour update finally takes 6-8 hours.
This is not good. Is there any other way to redirect traffic with IMMEDIATE effect and not wait DNS to propagate? Adding redirection inside the code is not really an option, because Azure service packages take an eternity to upload.
Thanks
Not sure what your full requirement here is, but could VIP swap do the trick for you?
You would deploy the alternate 'well be back' site to the staging slot and when you wish to update the service you'll use VIP swap to make that production whilst you update your service, which is now on staging with the latest build.
When that's ready you can VIP swap back and the new site is now in production?
Edited to add:
I take your point regarding wanting to leave the staging slot for rollbacks, makes perfect sense.
Another option could be to use the Traffic Manager -
Have your main application in one cloud service and your temporary landing page in another.
Configure a traffic manager failover policy with both services (main one first, alternative second).
when you want to go to 'maintenance mode' disable traffic to the main service and all traffic will get routed to the 'maintenance mode' one although there is some lag in propagating it measured in minutes rather than hours when I played with it a little bit just now - there's a DNS time-to-live setting available to you which defaults to 5 minutes.
When you're ready to come-back online re-enable the main site (and you can chose to remove the 'maintenance mode' deployment when all is working
There's a feature in ASP.NET to quickly stop serving content. If you put a file called app_offline.htm in the root of the site, it will serve that instead of regular content. There are details in this blog post.
Using it in Azure may be difficult. I would suggest using VIP Swap, but I see you don't want to do that. You could remote into each VM and manually add the file, though that could be painful. It may be possible to script it, but I don't know an easy way to do so.
Is there a place where you can reach the history of domain registrations?
To be more specific: How can I find out what other domains have been registered within a certain period of time?
I know there are paid services which allow you to find bulk-domain registrations. I wonder how they got those data.
thx in advance!
Typically they have an agreement with Whois registrars to obtain a dump of the database every night, and/or they run something like passive DNS to discover domains to put in their database.
StackMob allows you to setup a custom domain. All you have to do is add a CNAME record for a wildcard '*' pointing to stackmobapp.com
I set it up on my domain registrar 24 hours ago, but it still doesn't resolve. It is going to my web hosting providers server instead of stackmob's server when I type dev.mydomain.com
I kept my nameservers the same (ns1.myisp.com and ns2.myisp.com).
Do I have to change these to something else?
update: its been over a week and my dev.domain.com dont' go to stackmob.
You don't have to change your nameservers. Likely the dns changes hadn't propagated to your nameservers yet. It's been known to take up to 72 hours.
I figured out I have to use my registrars name servers, not my own in order to add A/CNAME records to it.
There is one problem with stackmob though, http://example.com doesn't forward to stackmob, only www.example.com and dev.example.com