3 ms·
I control the frequency of updates to the data. If something changes I see it. I decide whether I want to trust it. Usually in the case of a change I will do
by textmode 8y ago
I control the frequency of updates to the data. If something changes I see it. I decide whether I want to trust it. Usually in the case of a change I will do some research on the new IP address. "TTL" is a concept used for DNS caches. I do not use a cache.
- nstart 8y agoThis sounds interesting. Quick questions. 1. Is it possible at all to release some source code related to this? I know it's a big ask but I didn't want to leave without asking :) 2. Would it be ok to describe what this solution looks like a little more? Is it /etc/hosts being edited using a service? Is it at a deeper level? Do you use your own DNS server? I'd love to adopt something similar, hence the curiosity :)
- dvfjsdhgfv 8y agoI was using a similar solution but probably quite different than the parent. I first generated the list of entries using Tinyproxy (turned out it was much easier than inspecting local DNS cache): you install Tinyproxy somewhere and use it for a few days. Then take the log and cut the lines: CONNECT Sep 08 08:29:04 [18050]: Connect (file descriptor 6): DOMAIN [IP] So basically you almost have your hosts file ready, you just need to switch places of the DOMAIN and IP, cutting out all before and the brackets. A minute or so. I used it for a short time and never bothered to take care of the updates though. I guess I'd have to temporarily disable the hosts file and run an async DNS resolver such as adnshost: adnshost -Vq +Dt - filtering out the INET string to create a diff. It seems to much hassle to me though, to manually inspect DNS changes - I have so many things to do, I see no much reason to bother with every IP change on the Internet.