tag:blogger.com,1999:blog-2238516101365346732.post8452251285200558704..comments2023-09-20T17:56:42.131+02:00Comments on tech & sp: How to force a local DNS resolver to be used using resolvconfAnonymoushttp://www.blogger.com/profile/10693058812548733549noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2238516101365346732.post-18920643298028475732012-12-30T18:14:58.931+01:002012-12-30T18:14:58.931+01:00If you want to use the local resolver, Just remove...If you want to use the local resolver, Just remove /etc/resolv.conf<br /><br />This is explained in resolv.conf's man page.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2238516101365346732.post-63214553431116992802011-06-01T22:18:22.413+02:002011-06-01T22:18:22.413+02:00I haven't checked yet to be honest, but I gues...I haven't checked yet to be honest, but I guess it only allows 127.0.0.1.<br /><br />If you want to use other servers you could still put them above the 127.0.0.1 entry in the head file. Now if you have a bogus entry, like the one for localhost which is not running a nameserver, the resolver should just skip it, from my understanding at least. Correct me if I'm wrong there.<br /><br />And yes, this is a hack, but it should work.Anonymoushttps://www.blogger.com/profile/10693058812548733549noreply@blogger.comtag:blogger.com,1999:blog-2238516101365346732.post-4868135022330900172011-06-01T22:14:09.113+02:002011-06-01T22:14:09.113+02:00Adding TRUNCATE_NAMESERVER_LIST_AFTER_127="ye...Adding TRUNCATE_NAMESERVER_LIST_AFTER_127="yes" to /etc/default/resolvconf <br /><br />This suggests that this will only work if the nameserver you wish to always exist is "127.0.0.1". What happens if you wish to use some other DNS server? Does similar functionality exist, or is the option poorly named, and not requiring 127.0.0.1?Anonymousnoreply@blogger.com