New answers tagged web-hosting
Looking up the domain poc.co.in in the nameservers shows that it is registered with the co.in authority. It has two nameservers, ns1.poc.co.in and ns1.poc.co.in, both of which resolve to the same IP address 18.104.22.168. (This is bad practice; for two nameservers you should have two different addresses.) The nameserver on 22.214.171.124 is responding to ...
What you need are called glue records: What is a glue record? Essentially, without a glue record, your nameserver definition would be calling itself recursively; i.e., to resolve, ns1.mysite.com, first you have to resolve mysite.com, one step up.
That's no longer the case if using Apache 2.2.12 implementing SNI, a single address is no longer required per certificate. Hopefully we'll see more of this available to shared hosting now. https://www.digicert.com/ssl-support/apache-multiple-ssl-certificates-using-sni.htm
When it comes to website hosting, your main concern should probably be the amount of RAM as I've found from experience, not having enough can lead to all sorts of annoying problems and crashes, slow performance and downtime. You should be ok with any VPS server sporting 4GB of RAM or more, provided you're running linux. If they're just static WP sites with ...
Create a virtual host for each site. You can run them all on port 80 (or 443). This problem is exactly what virtual hosts are for. There's no requirement that each virtual host have a unique domain, only a unique hostname. See Name-based Virtual Hosts.
There are many options. A simple one would be to use ports, so that connecting to port 80 will show the current site, while port 81 would show the next site. But really, you should make sure you use hostnames.
Yes, that is entirely possible. Actually CGI isn't that much used in web developing anymore. PHP and other languages are mainly used for web developing.
If the website IP gets hit will the other IP go down? It will probably. DDoS works by generating high network traffic with a host, thus consuming all its bandwidth and creating a high CPU or disk load on it: if the traffic arrives on the server machine through any of the IPs it has, the other ones will be affected as well, if they share the same network ...
This answer is also "no", but it focuses a little more on the why. The target of a CNAME alias (or a NS delegation for that matter) receives no information from the other nameserver. The second nameserver receives queries as a result, but none of those queries convey any information that would indicate that such an action had taken place. You also have no ...
Yes. dig example.com axfr will perform a zone transer (or ls -d example.com if you use nslookup). You can then parse for CNAME records in the zone you just transferred. However, zone transfers aren't typically allowed willy nilly, so you'll need to allow transfer of the zone. You have the power to do that, right? Of course you do. Because only bad people ...
No, there is not. The main reason being that many/most domains (or rather, Name Servers) will not give you a list of all the records (names) they have. You'd have to brute-force all possible names on all domain servers everywhere.
Top 50 recent answers are included