I have a domain with nameservers that point to my server and i was replaceing the nameservers with external nameservers that forward the www to my server. I need to allow only domains that use my nameservers to acces my server.
Yes, You will have to disable " Allow Remote Domains" in your Tweak Settings. Once you disable it, You can add new domain on your server which is NOT using your server nameserver.
Related
I'm setting up a redirect server where users can input an alternate domain name, point DNS to my server, and configure it to redirect to their servers. My plan is to use the default virtual host in Apache to handle all the requests, route everything to a web application that looks up the place to redirect in a database.
I'd like to support HTTPS, but I can't figure a way to dynamically specify the certificate and key for each site. The only way that I know of configuring HTTPS is by putting directives for SSH certs and keys into a virtual host specific to that domain name. I'd like to store the certificates and keys in the database along with the domain name and have Apache call my web app during the SNI handshake.
Is it possible to have flexible, dynamic SNI under Apache?
I have a domain called qlink.co.in and I have a cpanel for this domain.
In cpanel I created a sub domain - server1.quicklink.co.in
In this cpanel in DNS zone editor I pointed this sub domain to my server1 like shown in image below -
Now I can access my http://server1 IP address. My link as http://server1.qlink.co.in/.
If I install ssl on my qlink.co.in domain which comes with unlimited sub domain option, then do I need to do anything on my server1 server or not? Will my subdomain link work with https?
SSL should be installed on domain from the server where your domain is pointing. As your sub-domain is pointing to other provider's server, you should install the SSL from that server.
It will not work, if you will install it from the server where your main domain is pointing.
I am using Cloudflare, and my domain is using their nameservers olga and duke.
I have A records for ns1.mydomain.com and ns2.mydomain.com and that is only thing which is revealing my real IP address, because i can not force clients to use CloudFlare. So I host their DNS.
If I enable CloudFlare for my NS1 & NS2 A records, will everything continue to work well?
Notice: NS1 and NS2 at registrar are will still be pointing to real IP address.
If you want to use Cloudflare you need to choose one of the following configurations:
Change your name servers at the registrar and use in Full mode,
Use via a hosting partner, or
Upgrade to BIZ and use a CNAME setup
Cloudflare Knowledge Base Article
Whilst Cloudflare can host the DNS records for your host - it will not proxy DNS records; Cloudflare will only proxy HTTP and HTTPS traffic.
If you wish to proxy DNS traffic you can use Cloudflare's Virtual DNS product. This acts as a firewall for your existing DNS infrastructure.
I just setup a brand new server at my host (NOT on a shared host btw), and apparently this IP was used previously and I keep getting requests in the apache logs for people going to that old domain (that has the same IP that has not been changed in DNS). Is there a simple way to tell Apache or htaccess to ONLY allow the domains I have defined there to serve my site, and ignore/drop/redirect others that aren't to my domain?
I am trying to create a third-level domain virtual host on my server. I hope the configs are set up correctly, but I am getting a ERR_NAME_NOT_RESOLVED error.
I have read that I have to "add DNS entry" somewhere so that the name would get resolved, but how do I do that? Where do I do that? The server is running on Ubuntu .
I suppose you get that ERR_NAME_NOT_RESOLVED error from Chrome. This means that Chrome is unable to find the subdomain in DNS.
You are correct, registering your subdomain in DNS will require DNS changes. Specifically, you have to add a DNS A resource record for your subdomain to become "visible" to browsers over IPv4. For IPv6, add an AAAA, too. Both record types point to an IP address and it will be the IP address of your web server. (Technically, you can also use a CNAME type record, but make sure to read up on how that works.)
Subdomain DNS will be served by the authoritative DNS servers for your domain, so you can register the required record(s) through your DNS service provider. If you are not sure who they are, look up the NS records for your domain, this will give you the list of authoritative name servers for your domain and you can work from there.
I understand you have already configured your Apache to work with the subdomain, so setting up DNS completes the setup process.