This issue has been plaguing me for days and I cannot seem to solve it.
I recently wanted to help out a friend with their 'Let's Encrypt' issues, as the software was throwing out a 404 error for a certain file it needed. After some digging I discovered some DNS inconsistencies between which domain linked to what IP.
Today I noticed that something really weird is going on. The set up looks like this:
https://websitename.com/ - 1st version of the website - Secure
https://www.websitename.com/ - 2nd version of the website - Not Secure
http://websitename.com/ - 1st version of the website - Not Secure
http://www.websitename.com/ - 3rd version of the website - Not Secure
I am not sure how something like this can even happen. By version of a website I mean an actual fully hosted website on a different IP.
I have not touched any of the htaccess files yet. I have checked all of the DNS settings for all of the given IPs but nothing seems to be wrong.
Sounds like the "www" CNAME record and the A record for the site are pointing to two different locations.
Problem
Just took a look at your DNS records. You have a record:
WWW record www.fish4parts.com A records are: www.fish4parts.com. A 91.121.225.216 [TTL=3600]
This record exists at ui-dns.com, which is separate from your fish4parts.com A Record.
Solution
If you cannot see the records on both of those NameServers (NS) you should give their support desk a call and ask them to remove the www A record from the ui-dns.com name server. If they are unresponsive you can always switch DNS providers at your domain. I use O365 for our domains, but previously used AWS Route53. The AWS product is super easy to use and very cheap.
Related
I am currently having issues with setting up an HTTPS domain redirect. I have a DNS URL redirect entry that points a few sub-domains to same-server URLs. For example:
docs.kipper-lang.org -> kipper-lang.org/docs/
play.kipper-lang.org -> kipper-lang.org/playground
The issue I am currently experiencing is that when using the subdomains, it mostly works, but it can only use HTTP. If I attempt to use HTTPS (like for example https://docs.kipper-lang.org) the redirect won't work and will get stuck apparently waiting for the HTTPS certificate (I think, but I don't know for sure, since it loads forever and gets a time-out).
So my DNS provider does its job for the most part as I want, but I am not sure how to add the HTTPS encryption to these redirects. Is there maybe even some DNS configuration or even middle-man service for redirects I can use, where these HTTPS encryptions are built-In? Since receiving a "Warning: Insecure connection" every time someone uses the sub-domains is a massive problem for me.
Note though that considering I am hosting on a GitHub Pages server, I am unable to do these redirects on the server side myself, as I can't use any code in this case.
I would greatly appreciate any ideas for fixing this or what I could use to achieve this another way.
Thanks in advance!
I'm probably doing something silly, but I can't seem to be able to figure this out.
I've waited over 24 hours for Firebase to validate my domain, but the status just stays at "needs setup" and "domain not verified".
Per other other related answers on StackOverflow, I use # as the Name for TXT, instead of what Firebase said to put there (I also tried the "acme-challenge.www.mydomain.com" for a while).
Here are my GoDaddy records:
Anyone got ideas what might be wrong?
OK. I think I got to the bottom of it finally (I'm really new to this domain business). I originally added www.mydomain.com and not the naked mydomain.com to the "connect domain wizard". And I believe since I didn't have a CNAME www pointing to # it could never have worked.
Now I just added mydomain.com to the wizard, and Firebase instantly validated the domain.
The status is now "pending" since it takes up to 24 hours to validate the certificate, but the site already works.
Make sure to delete the original A records using the name #. Only keep the A records that are pointing to the Firebase Hosting IP address.
EDIT:
Change your TXT value to google-site-verification=YOURCODE.
It must include google-site-verification=.
Add custom domain from GoDaddy to firebase hosting
Simple step-by-step solutions with screenshots are found here
I believe this question to be different form others because of the added Route53 complexity that is possibly contradicting the CLoudflare records.
I've recently moved to an AWS hosted service for a Wordpress site.
I'm using an EC2 instance with Bitnami installed, with Route 53 and Cloudflare dealing with the DNS records.
I should prefix all this by saying I'm quite new to this side of things and have followed multiple tutorials online.
Currently my site is working and functional. Everything is being routed correctly, however mail is becoming an issue.
I would like anything#domain.co.uk to be forwarded to my personal email address, and in addition, I would like to be able to reply to that email address.
Steps taken so far:
EC2 - Site installed.
Route53 - Pointed NS Record to Cloudflare
Route53 - Pointed CNAME record to domain.co.uk
Cloudflare - Records are pointed back to EC2 ip.
-- this is the bit that works (I'm just adding all info)
SES - Domain has been registered and verified
*Both Route53 AND Cloudflare have the MX and TXT records (I'm not sure if this part is correct)
*MX points to inbound....amazonaws.com
*TXT is the string
SES - Email address has been added and verified (this is my personal address - I 'think' I need to verify a admin#domain.co.uk but those are not coming through.
SES - Rule Set - One configured to send emails to S3 and then notify of email via SNS (this was my last attempt to simply get some notification!)
Currently when I send an email to my domain I get a bounce back:
To: myDomain <admin#domain.co.uk>
Subject: sdfsdf
Your message cannot be delivered to the following recipients:
Recipient address: admin#domain.co.uk
Reason: Illegal host/domain name found
I have other rules set up and in place at a domain level for sending to SNS -> Lamba as a mail forwarder but for now I'd like to get the simplest part working :)
WP SES - this is the plugin for wordpress that has been installed.
I think that perhaps the duplicate records in Route53 and Cloudflare may be part o the problem but I'm not sure which one is correct.
TIA for any help.
Guides I've followed are:
https://wpforms.com/how-to-set-up-wordpress-smtp-using-amazon-ses/
https://medium.com/#ashan.fernando/forwarding-emails-to-your-inbox-using-amazon-ses-2d261d60e417
I am trying to connect my firebase app in to a domain -where the domain purchesd from google.Need help to to do the setup for DNS configuration.
my app is working fine in firebase app.
firebase app is - https://.firebaseapp.com/
My Firebase setup
And
Google Domain (https://domains.google.com/) - DNS Configuration
1.Name servers
Default is "Use the Google Domains name servers" is it OK?, if not what to setup
2.Registered hosts
If anything, need to add- please let me know.
3.Synthetic records
If anything, need to setup - please let me know.
4. Custom resource records
I am trying to add two records but getting error while trying to add second record - is "Record already in use"
please find the screen shot
Update
Now I have added both the IP address, but still it is not working.
Click the little + icon to the right of the field where you're entering the IP address. That will open a second textbox that you can use for the second value.
I noticed in your screenshot
That you have #-------------.com (where I assume ----------- is your URL). You don't want that. You want simply # there (and www if you want to redirect www.--------.com as well). # means "this domain name", which in your case is ----------
Hope this helps!
This was really helpful but there was one missing thing I was still confused on. On the firebase docs page for this https://firebase.google.com/docs/hosting/custom-domain if you scroll down the page it give you an example of how to setup a google domain. It asks that you put in the following information.
I could not find any "verification value provided in firebase console" for a TXT record. I ended up just putting the DNS A record inputs and that worked for domainName.com and www.domainName.com
Addition to Editing and (+) adding records together. You might want to also add 2 records for # and and 2 for www.
I had same problem, every setup was right but site doesn't work.
Finally I removed the domain from Firebase and add it again without changing DNS setup, then problem resolved.
I have my production site's app pool to recycle every 2 hours or so. I noticed that when the first call to the site is made, the App Pool caches the base url (e.g. www.mysite.com). This makes sense as this is used to resolve relative paths in ASP.NET e.g. ~/MyFolder/MyPage.aspx, which is resolved to:
http://www.mysite.com/MyFolder/MyPage.aspx
However since the site can be reached via our host name e.g.
http://masdfg.my.provider.net
IIS thinks the url is
http://masdfg.my.provider.net/MyFolder/MyPage.aspx
As you can image, this causing an issue with SSL as well as others. How can I prevent this from happening?
UPDATE: The work around was to create a url redirect. If anyone knows how to prevent this let me know.
I hope I've understood your question correctly, but please do let me know if I haven't.
It sounds like the sole issue you have is that when you write the links to the response they sometimes reference the wrong root URL.
I notice that you use ~/ . This would resolve and write the entire URL to the response I think. It is better to use only / when writing links to the response.
So in your example you would write /myfolder/mypage.aspx. The browser would then resolve the / to mean that it's from the root address of the site, whichever that may be.
Like I said, I hope I've understood your question correctly and apologies if I haven't.
I know it's a long shot, but I've had a similar problem with my IIS setup. I solved it by going to the already mentioned "bindings" window through "Edit Bindings".
Then I removed all the not wanted bindings, then adding the hostname www.mydomain.com the server should answer to.
Finally I edited the windows hosts file at
%windir%\System32\drivers\etc\hosts
Adding the line
127.0.0.1 www.mydomain.com
This ensures that www.mydomain.com always resolves to the local computer.
After executing iisreset.exe as administrator my problem was over.
HttpContext.Current.Request.Url is not a cacheable item. That value comes from the HOST value of the HTTP headers. Which means it is passed in to the application from the request.
The only time it should take that second URL is if the requests HOST value was masdfg.my.provider.net
There are three possible fixes here. The first is to set your bindings and have any requests to masdfg.my.provider.net be forwarded over to www.mysite.com
The second, because your primary issue appears to be about SSL is to get a unified communications (UC) SSL certificate and install that on your server. This would be to cover the mysite.com and masdfg.my.provider.net domain names.
The third is to simply create a separate IIS site which points to the exact same production directory as the first one. Each site would have only 1 domain name it's responsible for.