We have a website that we recently revamped.
The domain it lived on use to have a CNAME record for # and www pointing to a different domain while the site was being developed.
We have now deployed the site (48+ hours ago) and chrome users who have previously visited the site are still being redirected to the domain the old CNAME pointed to.
The new DNS configuration is an # record pointing to the server and the a CNAME for www that also points to the same server (but a proxy).
We cannot figure out how to get existing users on chrome to pick up these DNS changes, if a user is to clear their browser cache, the site will work just fine. That said we cannot tell thousands of users to clear their cache.
Does anyone know how we can get users to pick up the new records?
The original TTL on the site was set to AUTO on cloudflare through the cloudflare proxy. I'm told this makes the TTL around 5 mins however its been over 48 hours and users are still having this issue. We have also purge the cache on cloudflare multiple times.
The answer was the TTL on each record, you just have to wait it out
Related
I have access to a Godaddy account where the company has all their domains. One of those I need to point to another web server running Apache. The person that used to work here before me solved this pointing to the new server IP using the record:
A # the.ip.addr.ess 1 hour
and in the webserver end I get it with Apache and as far as the webserver goes, it runs flawlessly. I even have some subdomains using the same A record structure.
But...now I have two issues. First, I lost email reception. I can send via smtp and webmail but anything sent to my domain gets bounced back after 24 hours, even if sent to an alias or forwarder.
The second issue is that I need to verify the domain with Firebase and even thou I created the TXT record, it cannot be found by Google. I'm sure it's because of the same reason.
What can I do? I understand a little about DNS and records, but not enough for this. I just want all html traffic to reach my webserver as it is now and keep the emails and other domain services working as they were.
As contacting Godaddy support, they said it is not their purview as it is external. I think they just don't know. Go figure.
Are you using GoDaddys NameServers? If not and these are pointing elsewhere no matter what DNS records you set in GoDaddy won't be picked up during DNS lookips. This may explain why the TXT record verification is failing. However if this was true changing the A record wouldn'd disrupt DNS.
# just means the root domain so no subdomain/prefix, mydomain.com.
www is a common subdomain used so you could have an A record which like:
A www the.ip.addr.ess 1 hour
so www.mydomain.com would resolve to the.ip.addr.ess
MX records are used to direct emails to your mail server. Make sure this is pointing to the mail server. If it's pointing at your A record then updating the A record will disrupt this.
Set the MX record to point to the.ip.addr.ess rather then mydomain.com, or an A/CNAME record other then your root domain (which you are updating)
Other considerations may need to be taken, if you have an SPF record (TXT record) this may also need updating, depending on it's current value.
I finally found what I had to do. I needed an A record named 'mail' pointing to the original Godaddy server IP address.
A mail my.ip.add.ress. 1 hour
Thank´s for all the help.
I deployed a node app on heroku and pointed a custom domain to it from namecheap. When I type my domain in it will load a page that says "Theres nothing there, yet" and changes the url to domain.com.herokudns.com
After looking around for 2 days I came back to the same solution, I created two cname records on namecheap that pointed to the "domain.com.herokudns.com". The cname records automatically place a period after this target, when I place a period after my domain when searching, my website loads.
Is there a way to fix this? I've seen people with similar problems but I find it weird that my site will load both with www and without if I have a period at the end.
I had to change the cname record to a www name with the target of [herokuappname].herokuapp.com and add a url redirect # to http://[www.yourdomain.tld]. After clearing my cache this worked.
I deployed my node js app properly on heroku and it's working fine with the heroku provided domain name.
Now, I'm trying to link it with my personal domain name. On the heroku website, in the settings section of my app hosted by heroku, I have setup the domain name to be my-app.com and my heroku dns is set to my-app.com.herokudns.com
In 1&1, I have registered a domain name my-app.com that I redirect to www.my-app.com
Still in 1&1, I have then created a sub-domain called www.my-app.com, in which I have set the DNS CNAME to my-app.com.herokudns.com
I saved everything but when I go to www.my-app.com, the url shows www.my-app.com/defaultsite in which the content shows a heroku generic page telling me There's nothing here, yet. Build something amazing.
Could anyone has a clue on what may be missing to connect to my app ?
DNS changes take time to propagate through the network. Very often you'll have to wait before seeing them take effect.
This can be somewhat mitigated by setting your records' time to live (TTL). This value specifies an expiry time for your records after which cached values should be re-fetched from the authoritative server:
Shorter TTLs can cause heavier loads on an authoritative nameserver, but can be useful when changing the address of critical services like Web servers or MX records, and therefore are often lowered by the DNS administrator prior to a service being moved, in order to minimize disruptions.
Note that if you are planning to change a DNS record its TTL should be lowered far enough before the change is made that old values will already have expired. For example, if the record you plan to change has a TTL of 86400 seconds (24 hours) you should decrease it at least 24 hours before modifying its value.
I have recently set up my domain, but my problem is when I navigate with/without www, the results are inconsistent. They are supposed to point to the same page, but sometimes, the www site has broken links to non-www components (e.g.: when I load http://www.my-domain.com, and if I have a resource referred as http://my-domain.com/navi.css, it breaks)
Have tried 301 rewriting, but it's not always consistent. What do I need to do to ensure 100% uptime for my site?
This could be because of a couple of reasons:
Your DNS has not propagated yet, meaning if you recently just changed DNS on the domain name give it up to 48 hours and flush cache from your browser.
The domain DNS is pointing to different IP addresses from your www. or * A records.
There is a problem with the hosting configuration (unlikely if you are using CPanel or any hosting control panel as this is mostly automated).
Also you should pick either with or without www for consistency and better SEO results. Pick one and stick to it.
I am trying to create a subdomain using DirectAdmin. The subdomain will be finance.nickputman.com
I appear to have successfully created the subdomain in that there are A records for finance and www.finance showing under 'DNS management', and when I carry out an online DNS propagation check for the A records, all reports come back as successful.
And yet when I try to visit http://finance.nickputman.com I get a server not found error. http://nickputman.com/finance works OK.
Is there another step I need to take to get this working?
It takes some time before new/changed dns records are fetched by your local dns cache (depending on the TTL values of the old records). Manually clear the dns cache to force an update.