See 32 Million Digits of pi here
After many months of strugle, my new DNS Resolver and Nameserver now works, use
dig @ns1.hng.ovh ping.hngto test it, you should see demand.alpha.hng.ovh, demand.beta.hng.ovh and non.charlie.hng.ovh, which are the root HNG. nameservers, for me to use it, i add
22.214.171.124in /etc/resolv.conf and with windows, first dns server is 126.96.36.199 and secondary is 188.8.131.52, as it it is good to have a backup, but now TEST.HN.FYI now points to the nameservers one.hn.fyi, two.hn.fyi and b.hang-servers.ga (ns1.fr.hang.glue & ns3.bl.hang.glue) for maximum failover capabilities , i am also working on internal TLD's like .hng, but with linux using 2 nameservers 184.108.40.206 & 220.127.116.11 interferes with interal TLD's, so i stick with
#/etc/resolv.conf nameserver 18.104.22.168 # Main Master nameserver 22.214.171.124 # Slave ZoneHowever, sometimes they are not very reliable, so always have a backup (126.96.36.199), even though for permanant changes, you should change your nameservers in /etc/network/interfaces or wherever your system network config files are located, but for a GUI where more internet is used, rather than just command line, use your ISP or Host provider's DNS server as secondary and HNG's as primary (for tld resolution) find your UK ISP providers dns server here, or just ask them, as they are on the same network as you, are are probably the fastest dns server for you.
Below are the addresses for some services;
wget https://www.hn.fyi/~hng/d-lat-install.shthen chmod it and run it as root, then enter your home directory, it will create .ns which is used by the script, by the script, it then determines the lowest latency nameserver, and uses dig with it, the usage is...
d-lat [record type e.g a] [domain]
curl -L https://hn.fr.to/scripts/speedtest/speedtest.py | python
download [user] [url]What it does is download the file in [url] to /home/[user]/Downloads, it is just a utility script to make things easier.