To insert multiple keys into a registry folder (e.g. Computer\HKEY_CLASSES_ROOT\....\....), I basically have to manually right click → New → Key for each key.
This can get annoying and redundant, especially at times when I need to insert more than 10 keys.
Is there a way to insert multiple keys into a registry folder using the default GUI?
Is there a cmd command to do that?
RFC 1034 requires us to assign at least two IP addresses for DNS servers. However, redundancy can already be achieved by a single IP address if we use anycast addressing. BGP anycast seems to scale well into hundreds or even thousands of servers.
If so, why do we still need multiple IP addresses for DNS servers? Does it actually enhance redundancy (contribute to availability) if we already have anycast in place, or is it just a myth?
What problems and errors can we expect to face if we only use a single IP address?
By that, I mean totally omitting secondary DNS addresses, or using a bogus IP (e.g. 1.2.3.4) for the second address when some setups require at least two.
I was told that the DNS for my domain is unreliable, so basically I was wondering
Could I set my secondary DNServers that points to another webhost altogether ? :
ns01.host-FOO.com
ns01.host-BAR.com
ns02.host-BAR.com
ns02.host-FOO.com
Or would "mixing-and-matching" as such cause things to go wrong ?
Simple Failover markets itself as:
continuously monitors your servers to find out which are up and which are down, and then it dynamically updates your DNS records accordingly so that your domain name always points to a functional server.
From what I know, updating DNS records can take hours to days to propagate. As such, even if they dynamically update my server's DNS records, my users would still have to wait a few hours before they would see any change right?
If so, how could "Simple Failover" work?
When does the NS lookup chain stop?
For example, if I go to A.com and the NS for A.com is ns.B.com.
Then the client (browser) needs to find out the IP for B.com, NS for B.com is ns.C.com.
Then the client needs to find out the IP for C.com, NS for C.com is ns.D.com.
Then the client needs to find out the IP for D.com, NS for D.com is ns.E.com..
I mean where does this chain stop exactly?
I was trying to understand the inner workings of DNS.
To clarify things, when I say the root domain I mean the root domain without a name.
So when I type http://www.example.info, it will check the top-level domain .INFO and find out which IP example points to, and all is good.
Yet how does the browser know the IP of the top-level domain .INFO ?
So I was thinking the browser contacts the nameserver of the root domain. And the root domain will tell the browser .INFO is at 123.456.123.456.
But Wikipedia states:
Although any local implementation of DNS can implement its own private root name servers, the term "root name server" is generally used to describe the thirteen well-known root name servers that implement the root name space domain for the Internet's official global implementation of the Domain Name System.
I was wondering why is the root name server not the name server of the root domain ?
Why isn't the root domain also a name server?
I was pinging my site with DownOrNot and it is reporting that my website is down from all locations.
Then I pinged it with JustPing and it is reporting that my website is also down from all locations.
However, http://qweop.com definitely works fine for me. I tried visiting the site through a couple of other proxies and all of them are finding http://qweop.com online.
What's causing the issue here?
Why is DownOrNot and JustPing reporting that my website is down?
Update: Note: this is a test site. I no longer own qweop.com.