Hot answers tagged

3

The simplest way to do things is to have both sets of nameservers (old and new ones) supply the zone for some time (with the same data), so that the switch is handled without any interruption. Then what counts is the parent zone TTL on the NS records, as this may dictate for how long recursive nameservers may continue to hit old nameservers, which is why it ...


3

It turned out that HSTS headers were being served by the previous hosting. HSTS set all HTTP requests to example.ca to be internally redirected to HTTPS before being sent. Because custom domain HTTPS was not yet configured for the S3 bucket, the HTTPS request was timing out. Note that S3 does not support custom domain HTTPS directly, only through ...


3

I'm afraid I couldn't help you with the complications of setting up a Postfix mailserver, however with regards to your questions about the DNS records: The MX record you have created looks fine, provided that you have checked that (a) you have no other MX records with a priority less than 10, and (b) you have definately also got an A record setup for titan....


2

You are checking your DNS records by using Who.is. A big problem with this is that Who.is does not always perform a Whois lookup or DNS record check live, in real time. They also appear to cache Whois data and DNS data for an unspecified amount of time. To check your DNS records in real time, you'd want to use dig from the command prompt (if you have this ...


2

The first thing you want to do, is reduce the TTL (Time to Live) on your DNS records to be as small as acceptable. This will keep cached DNS servers from holding onto stale data for too long when you switch. Next, I assume your web site is going to be moving to a new IP address. There is no reason switching the site to a new host IP address has to happen at ...


2

You need to get an Elastic IP Address and associate it with your EC2 instance. Then you can point your domain to that IP address. You can do this without using Route 53.


2

The problem was that although I modified the search.widget.com CNAME to point to drvevtora80lk.cloudfront.net I forgot to add search.widget.com as an alternate name within my CloudFront distribution, added that and it now works.


2

Masking, no. Redirecting, yes, with help from S3. You can create an empty S3 bucket named abc.example.com, configured to redirect all requests to another host, xyz.example.org. Configure an A record in Route 53 for abc.example.com, set "Alias" to "Yes," and select the abc.example.com bucket from the drop-down list of alias targets. Note that the bucket ...


2

MX record: *.example.com matches everything but the naked (no subdomain) domain. So no MX for example.com. Aparently a friendly MTA will try the A record, which used to work for me, since it pointed to the EC2 handling my email. Long story short. Removed the *. from the MX record and it worked. I hope this will save someone a couple of hours of trying ...


2

Make sure to only use one version of your site whether it be www or without www. It's preferable to redirect one version to the other so that there are no duplicates. You can do this in htaccess, and a lot of domain registrars/webhosts allow you to set the preferred version. If your site does have duplicate versions of www and non-www, you can tell Google ...


1

Just accesed your site. It's working fine. I guess the problem that you faced was this: Due to large TTL DNS servers across the world take time to update CNAMES and A Records. probably the DNS server that you accessed did not have the CNAME directing to your server. Now it must be probably up over there too. Check DNS Checker to check your domain details [...


1

The problem was changing "Site URL" to the correct URL and then clearing my browser cache. This can be done in admin>settings>general.


1

You can't delegate the root of a zone this way. You need to find the other option at your regstrar's site where you set the authoritative nameservers for your registered domain. Select Domain List from the left sidebar and click the Manage button next to your domain: Find the Nameservers section and select your preferred option from the drop-down ...


1

Step 1: In the AWS Route 53 console, get the name of the four name servers they provide, you will need these for step two. Step 2: Log in to the website of the Registrar from whom you bought your domain name. Input those four name servers provided my Route 53 into the Registrar's management console. You do not need any other record of any type whatsoever ...


1

Your DNS records are not configured correctly. There are A records that are still pointing to a different location while the CNAME is pointing to your Bucket. Remove you CNAME that is pointing to the buckets and edit the A records make sure to set yes to ALIAS and remove the wildcard A record the one with the * You should only have 2 A records and both ...


1

You unfortunately do not provide the name involved so people can not really troubleshoot things except by throwing guesses. Here is my generic (not exhaustive and not all possible corner cases) quick but logical list of steps to execute in order to check for timeouts, and you should complete, in that order, each step successfully before going to the next ...


1

GoDaddy uses email servers that are not hosted on the same server as your web hosting. This happens to be rather common for many shared hosting web companies. In order to use GoDaddy's email with your domain you need to point your domain records to the correct addresses. Pointing to your domain is not the correct procedure as you will need to point your ...


1

After some sleep, I got it working. I was missing one step. I had already established a hosted zone for mysite.com, within route 53. When that was set up it was handed a set of nameservers from aws. I simply edited those and replaced with: ns1.mypath.net ns2.mypath.net ns3.mypath.net ns4.mypath.net That was wrong, since the original nameservers are now ...


1

All a CNAME record does is handle address resolution. In otherwords if client.bigmultisite.com has an A record of 1.1.1.1 if you then CNAME www.clientsite.com to client.bigmultisite.com the users browser will be given the IP of 1.1.1.1 to go to with the domain name of www.clientsitecom. What you would need to do it either have it running as the only site on ...


1

Its should not impact SEO. You just have to use a custom domain for your Elastic Beanstalk application, such as http://myapp.example.com, by creating a CNAME with your DNS provider that maps your custom domain name to your Elastic Beanstalk URL.


1

I generally set up a sub-domain name, though it is not necessary. The sub-domain name does not matter. I use mail, but titan is perfectly fine. You want to either set up your sub-domain name using either a CNAME pointing to mydomain.com.au or as an A record just like mydomain.com.au. Either way you chose, it does not matter. Next you would set up a MX record ...


1

Here is a summary of the Answers from ServerFault's Can you lookup a domains past nameserver & mx record history?: Omid Kosari says: http://whoisrequest.org/history/ This one is really cool . No registration needed . Professor Falken says: whoisrequest.org only works for com, net, org, info, biz and us domains. For others try using http://dnshistory....


Only top voted, non community-wiki answers of a minimum length are eligible