I am setting wildcard nameservers that are meant to resolve any dpim pointed to them. I need for my domain parking service.
I was able to set wildcard A records with BIND, and this is good. However, some registrars seem to look for the SOA records, and it seems that BIND doesn't allow creating such records. Therefore, I need to switch to another DNS software, but I can;t find any that supports wildcard SOA records.
I am running a CentOS 6.5, 64-bit server with Plesk 12.0.18, and need to install a wildcard SSL for one of the domains/sub domains hosted on this server.
So you have the csr and private key installed (and domain.crt?), you just need to open..
I have a Cpanel DNS-ONLY secondary nameserver at ns2.frozenblues.com that returns A records but does not return MX records, despite the zone files having correctly synched with the primary WHM (11.11.0)/Cpanel server (at ns1.frozenblues.com). Again, the files in /var/named are all correct on the DNS-ONLY server incuding the MX info, and it is returning A records, but not returning MX.
One of our servers was incorrectly set up before migration occurred. Now the ns records are incorrect on many domains' zone files. Does anyone have or want to let me hire you to write a script to change all the ns records and that are currently ns1.something to dns1.something. It can't be for every domain on the server, just the ones pointing to the incorrect ns, as some of them are correct. Linux server.
DNS records in DNS server and DNS records in Hosting Server.
So, I have one VPS acting as DNS server and few VPS for domain site hosting.
I have it now (working ok) like below but can You please comment if there is something 'extra' or something I should reconfigurate (or delete) to make better performance/clear
ns1. & ns2.server.com are registrated and working ok
DNS server DNS Zone for <customer.com> (cPanel output):
Zone File for customer.com $TTL 14400 @ 14400 IN SOA NS1.server.com server.server.com
customer.com 14400 IN NS NS1.server.com. customer.com 14400 IN NS NS2.server.com. customer.com 14400 IN A 11.11.11.11 localhost.customer.com 14400 IN A 127.0.0.1 customer.com 14400 IN MX [0] customer.com. mail 14400 IN CNAME customer.com. www 14400 IN CNAME customer.com. webmail 14400 IN CNAME customer.com. ftp 14400 IN A 11.11.11.11
Hosting server DNS Zone for <customer.com> (Plesk output):
I have Plesk installed on the master nameserver ns1.example.com, the dns slave manager extension installed, a working slave ns2.example.com and Plesk installed with working WHMCS autocreation of customers and subscriptions on a shared hosting server web1.example.com. I feel there's probably something obvious that I'm missing, but I can't figure out how to autocreate DNS records on ns1.example.com for customers on web1.example.com when new accounts are created.
I have just moved away from Kloxo Hosting, and I am a bit confused as to how I go about setting Client domains to use the (Already Registered) Nameserver Records I have created on the server.
You see, when I create a customer, the template adds the domain with it's own nameservers, ex: (ns.customerdomain.com -> 0.0.0.0) I don't want this to be the case.
What I would like to achieve, is for all my client's to have their NS records pointing at the NS records I already have registered on the server.
The reason for this is, when I submit the registration document to my local registrar, I have to specify the nameserver address for the domain, however, I only have 2 IP's on the server. I cannot glue every customer's domain FQDN to an IP.
We have a lot of unused domains that we'd like to setup domain parking for.
To keep it simple, we'd like to just change the namesevers to ns1.domainparking.com and ns2.domainparking.com (not real nameservers!) and the domains would then automatically show a simple web page.
We use cpanel servers and are wondering how easy this is to do? I've seem mention of wildcard dns? Is that the answer?
I run a free hosting service where users can sign up for a free blog.
With wildcard DNS and A entry, the users that sign up for a blog get the addy: theirblog.mydomain.com
This all works but there is no scalability. I have reached the limit of what my server can take.
If possible I would like to run multiple servers with just one domain.
So that when server 1 reaches its limit, it is possible to sign up new users that gets theirblog.mydomain.com (same domain) but now its physically stored on server 2.
Is this possible if you use wildcard DNS for the users subdomain sites?
I am quite new at this. I know there are ways to manage one domain on several servers, but is this possible too with this setup using wildcard dns and subdomains?
I bulk register .com names for future use, and out of all the ones I use, only about 30 have actual sites, whilst I have about 200 that are just not doing anything.
I have seen places like godaddy who whatever website people visit just gets fowarded to a landing page, and I have set it up so the nameservers all foward to my dns servers (I manage my own infrastructure).
I have seen through IIS it is possible to have a "catch all" website where any traffic goes there, however, how do I set this up in DNS?
I tried creating a zone called .com but that didnt work! and I really dont know what I should do!
Does anyone know.. if you have a wildcard ssl cert for *.domain.com meaning you can use anything.domain.com can you also use anything.anything.domain.com (ie. unlimited subdomain levels) ?.
so the serverB A record is on serverA which is fine (i am aware it's a risk if serverA goes down).
If I'm setting a sub domain of serverB such as site1.serverB.maindomain.com I have to setup an A record on serverA for the subdomain and I don't want to have to do this every time.
Is there anyway I can setup a wildcard A record for subdomains such as: *.serverB.maindomain.com
Now that I have relieved a lot of frustration I can talk about my issue. We have a cpanel server and are trying to install a wildcard ssl certificate on it. As you could tell from above its not working out so well.
The cert was ordered an installed as *.domain.com . It works great on https://domain.com and [url]
However, when I do [url]its an epic fail. Its a seperate cpanel account even with its own dedicated IP address. I look in the httpd.conf file and see the :80 entry however, I need to add a :443 entry in a way that cpanel/whm will not change it next time i add an account.
When I try to install the SSL certificate in WHM on jeff.domain.com it tells me the domain does not match. So I am asking how do I get this to work? I have searched for quite a while on the net and have not come across anything that works.
one of my customers asked me if i can enable the WildCard DNS for him on Apache. i just want to know is it any security issue with this if i enable it? can it be a security problem for my server if i enable it?
I am not that much of a dns/server expert, and I really need help setting up wildcard dns for domain names.
I have 1 parent domain zone file. Let's name this domain "parentdomain.com". Now this domain is set up with private nameservers of ns1.parentdomain.com and ns2.parentdomain.com and everything works fine.
What I want to do is now have the ability to put ns1.parentdomain.com and ns2.parentdomain.com into any other domain on the web and make it forward to this Parentdomain.com web root.
How do I do this WITHOUT adding a zone file for each of these individual child domains?
The thing is that I have a project where I don't know which domains will have nameservers set to ns1/ns2.parentdomain.com, but I want them all to forward to the appropriate directory.
got the VirtualHost entries for Appache, so each Domain points to a folder.
The (Windows-)DNS runs on the server, means i have to create a new DNS Reverse-Lookup and Folder for each Domain seperatly, but this workflow appears to be pretty stupid..
Now my question:
Anyone can tell me how to setup somwhat a "Wildcard / Catchall DNS", and also "Catchall VirtualHost", so each Domain is automatically pointed to the right folder? Any scripts needed for that?
"Wild card sub-domains will not work with our standard shared hosting accounts. although the DNS configuration is available to have any sub domain not listed direct to an IP address the actually hosting account will not recognize a wild card DNS entry unless you have manually added the specific name of the sub domain."
The only part I understood was the first line. Maybe it is my lack of hosting related knowledge or maybe because English is not my native language, the second sentence is very confusing to me.
I've just got a new server with WHM/cPanel. I was upset that after I installed my *.example.com wild card SSL cert successfully that it didn't operate how I expected.....