Related

Tool Instant DNS Lookup Tool Tool
Meteor/Nginx on Ubuntu 16.04 forcing non-www to https Question Question
Domain is not connecting to droplet. Question Question

Question

How can I get a DNS sub domain to a different NGINX server without https?

Posted September 2, 2016 2.4k views
NginxDNSUbuntu 16.04

I have followed the How to set up and test dns subdomains tutorial in order to redirect a subdomain to a nginx test server.

This tutorial is outdated and the panel looks somewhat different now.

My zone file looks like this:

$ORIGIN geolytix.com.
$TTL 1800
geolytix.com. IN SOA ns1.digitalocean.com. hostmaster.geolytix.com. 1472841549 10800 3600 604800 1800
geolytix.com. 1800 IN NS ns1.digitalocean.com.
geolytix.com. 1800 IN NS ns2.digitalocean.com.
geolytix.com. 1800 IN NS ns3.digitalocean.com.
*.www.geolytix.com. 1800 IN CNAME www.geolytix.com.
*.ngx.geolytix.com. 1800 IN CNAME ngx.geolytix.com.
geolytix.com. 1800 IN A 178.62.114.162
www.geolytix.com. 1800 IN A 178.62.114.162
ngx.geolytix.com. 1800 IN A 138.68.141.104

When I test the host ngx.geolytix.com I get the right address returned. But when I put the address in the browser I get a redirect to https://ngx.geolytix.com.

I have no clue why this is happening?

Add a comment
By:
dbauszus

Related

Tool Instant DNS Lookup Tool Tool
Meteor/Nginx on Ubuntu 16.04 forcing non-www to https Question Question
Domain is not connecting to droplet. Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
ryanpq September 2, 2016

I was not able to replicate this. Going to http://ngx.geolytix.com did not result in a redirect and instead showed the nginx default page. My guess would be that you have a 301 redirect cached in your browser or on your network. I would recommend testing this by trying to open the page in a different browser or from a different computer or smartphone that has not previously visited ngx.geolytix.com

Reply Report
  • dbauszus September 4, 2016

    You are right. I have a 301 on the domain geolytix.com on the production NGINX server.

    Clearing the browser cache did indeed resolve this issue. Thanks for the suggestion. I wouldn’t have thought a browser will cache a 301 on a domain for new sub domains. Good to know. Thanks.

    Reply Report
dbauszus September 4, 2016
[deleted]
Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help