For my needs, I actually like this method. Here is how someone else solves the problem of changing IP addresses. You have to do what best suits your needs, whatever they are. "How does that work if everyone has a hosts files?" At work I maintain a DNS server with 2000 entries on my network, which is actually hosts file powered, but again I use dnsmasq for the DNS server rather than rsyncing that hosts file to 2000 machines. It's one step better than a plain text file, as there's a standard based way to remotely query it. I maintain DNS entries for my home network of a dozen devices - I host it on my mikrotik, but it's handy to have, when I type "ssh laptop" rather than remembering if it's on. Which isn't in my hosts file or dns cache, and I've never visited before) Now it's ddg and assume they have a website. I maintain a list of every phone number I am likely to use on a repeated basis, but sometimes I need to look up a phone number I don't know (in the old days this was a phone book locally, and directory inquiries further afield. If I say "check out this interesting story on ", you don't have it in your hosts file, how do you get it? How does that work if everyone has a hosts file? If I move a server from one IP to another, I change DNS, and in $TTL time everyone's pointing at the new server. If you know which DNS names you will need to know, then yes, there's no need for more than a hosts file. Assuming at best I will not live much longer than 100 years, I could not and will not explore them all or even a significant fraction.
This is many, many more domains than I will ever need to look up. For example, using "consumer" hardware, I can fit all the major ICANN TLD zones on external storage and the entire com zone (IMO, by far the most important) in memory. They have also changed since the advent of DNS. Times have changed since the advent of HOSTS.
If you think about this, it may cause you to question the necessity of DNS for such users. I believe most users will never come close to intentionally accessing "millions" of IP addresses in their entire lifetime.FN1 I could be mistaken and it would be interesting to learn of a user who can dispel this belief.įN1. I maintain a database of every IP address I am likely to use on a repeated basis, in several formats, with kdb+ as the "master" format. I would be interested in reading about a user who visits "millions" of websites or otherwise needs to do lookups on "millions" of domains. There is a comment in this thread where someone asserts that HOSTS was never designed to handle "millions of entries". I have never had a concern about the speed of using HOSTS. Zone files are more flexible than HOSTS files, but I still use HOSTS as well. I use nsd as well which uses BIND format. I have scripts and compiled utilities that transform HOSTS file to tinydns format.
0 kommentar(er)
