I recently migrated a site to a new hosting service. There were some problems with the SSL certificate that needed to be ironed out in the new location, so I turned off HTTPS until those issues were resolved. They are resolved now, and so I updated the .htaccess file to direct all requests to use HTTPS. But after making that change, I get the IP address of the old hosting service when I ping the URL.
Checking the URL at whatismydns.net show that the new nameservers have propagated, so I have no idea why I've reverted to the old IP address. Will it change back? Do I have to re-update my nameservers?
The domain in question is oaklandoctopus.org.
Related
I have a godaddy domain name and I added it to my nodejs app hosted by heroku. However, when enter my new domain name in the browser I get the ERR_TOO_MANY_REDIRECTS.
I have added my domain name to the heroku app. This action then generates a DNS target say .herokudns.com.
I then configured my domains godaddy DNS management to have the CNAME WWW value to be .herokudns.com the DNS target provided by heroku.
I then configured the forwarding and set the values as follows.
FORWARD TO: http://.tech
FORWARD TYPE: Permanent (301)
SETTINGS: Forward only
Update my nameservers and DNS settings to support this change. => TRUE
This seems to be the way to get this done however I keep getting the ERR_TOO_MANY_REDIRECTS error. Does anyone have a good solution to this problem.
I figured it out, the usual missing letter problem that occurs every once in a while.
I've created a Google Site on my personal account and am trying to publish it to my custom URL hosted on Google Domains through that account. Per the instructions I did this using the Publish settings... dialog and entered the custom URL:
The normal sites.google.com/... URL works fine, but the custom one doesn't:
My DNS settings in the Google Domains console are pretty simple, just some G Suite mappings and what looks to be the resource record automatically populated by Google Sites:
How can I fix the DNS_PROBE_FINISHED_NXDOMAIN issue to get the site forwarded correctly?
The DNS PROBE FINISHED NXDOMAIN problem was started due to incompatibility of IP addresses with computer DNS. To be more technical, DNS converts all messages from a domain into a form of IP address. The real problem arises when someone enters a URL in their browser; it's up to DNS to find a server with the appropriate server IP address. While in the general case, the search process is directed to the target site, but if the DNS fails, this will produce an error. Changing DNS server to Google DNS or OpenDNS , or remove all cookies and cached files on your browser will help to resolve this issue immediately. Like any other error, there are several ways you can solve these problems by yourself:
Release or Renew Your IP Address
Change DNS server
Restart DNS Client service
Reset hosts file
Reset Chrome Flags
Reset Winsock program
I wanted to use CloudFlare for my website (hosted on Microsoft Azure).
I have added my domain to Cloudflare, and changed my domains nameservers to the ones I got from Cloudflare.
Furthermore, cloudflare imported my current DNS settings which are the following (my domain has been replaced with domain.com):
I thought the migration would go smoothly, however, when I go to www.domain.com I get the error:
The webpage at http://www.domain.com/ might be temporarily down or
it may have moved permanently to a new web address.
However, when I refresh a couple of times it finally loads the site.
If I go to domain.com (no www-prefix), I get the error:
domain.com’s server DNS address could not be found.
What could be going on?
For the first issue...if you are seeing inconsistent responses from your Azure Website, they you should raise an Azure support ticket.
For the second issue...try verifying the CLOUDFLARE DNS resolution via http://digwebinterface.com, both via a recursive DNS service and by querying against the CLOUDFLARE name servers directly. If the latter is working, there must be a problem in your DNS delegation (check name server settings with your registrar, try also a delegation validation service such as http://dnscheck.pingdom.com/). If the latter is not working, you'll need to take it up with CLOUDFLARE.
You need both # and www CNAME specified in your host records. Not just www.
the refresh is normal after you make a dns change. The browser keeps the dns lookup in cache, so if you visit the site on another browser you won't have to do a refresh. Just clear your browser cache when you want to see dns changes, but some edits could take 15min or longer to see changes.
My company changed names recently, so along with that came a new domain. Both the old site and the new site are HTTPS and are on the same server using separate DNS entries.
I setup a 301 redirect which works great if people go to oldsite.com, but if they go to https://oldsite.com they get an SSL error.
Is there any way around this? Hopefully through DNS, server config, or htaccess file.
With TLS/SSL, only one certificate can be presented by the server per IP address. So if oldsite.com is using the same IP as newsite.com, the certificate for https://newsite.com will be the one sent to the client, which will (by definition) raise an SSL error for https://oldsite.com.
To have both oldsite.com and newsite.com both active, you'll have to have separate IPs for each. These can reside on the same server, with some (possibly complicated) routing configuration depending on your server's OS, to ensure requests to each IP are replied to from the same IP. However, even with DNS entries for both, you cannot share an IP address with multiple HTTPS domains.
Edit: You could also use virtual domains (exact config dependent on which web server you're running) to present the certificate for oldsite.com, then send the redirect after the TLS session is in place. I'd have to know which web server you're using (Apache, Nginx, Lighttpd, etc) to give a config example, though.
I recently began migrating an old site to Drupal, and the hosting service I was using was really cheap and wouldn't have worked with all the modules I installed. I already hired a hosting account at a new (Drupal friendly) service and changed my DNS settings to point to their servers,... but the problem is that it's been a couple of days and the domain still points to the old account. When I whois my domain I can see in the domain servers section that the new servers show up, but if I nslookup or dig the domain I find the older servers. How could this be?
There are few possible reasons:
Your ISP is still resolving you domain name to the old servers
You have a local DNS server with a long TTL
You have a record in your host file pointing to the old server
The DNS change wasn't done correctly