Once upon a time, Edward Peschko <[email protected]> said: > IMO, its pretty silly that resolv.conf makes it so difficult for you > to do this. They make the implicit assumption that you have access to > the machines in question to make such changes.
The standard resolver is "dumb" on purpose, to be as simple as possible. It was never intended to fulfill every possible DNS need. As has been pointed out, it would be trivial to do what you want with a local resolver daemon (dnsmasq, unbound, bind), and point resolv.conf to 127.0.0.1. If you have access to edit /etc/resolv.conf, you also have access to the "nameserver" (aka the local machine). I don't know why you are trying to make this so difficult. -- Chris Adams <[email protected]> _______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
