tomatoyohe
asked on
lwresd.conf - Lightweight Resolver Daemon configuration guidelines
I am interested in configuring lwresd. Is /etc/lwresd.conf used in lieu of /etc/resolve.conf or in addition to it?
What is the format of an lwresd.conf file? What are the keywords and values that are allowed?
The manual page for lwsresd makes no mention of a -c option only a -C, however entering "lwresd --help" reveals that "-c" is a valid option and the description implies that lwresd.conf serves a different purpose than resolv.conf.
I have never found any example of a lwresd.conf file on google. I have found that a zero length /etc/lwresd.conf file was installed somehow on my linux.
In general, using "rndc" I am unable to prove that "lwresd" is working correctly and I suspect that the root cause of the issue is that the resolver libraries and lwresd.conf are not on the same page and that a properly configured lwresd.conf remedy this.
What is the format of an lwresd.conf file? What are the keywords and values that are allowed?
The manual page for lwsresd makes no mention of a -c option only a -C, however entering "lwresd --help" reveals that "-c" is a valid option and the description implies that lwresd.conf serves a different purpose than resolv.conf.
I have never found any example of a lwresd.conf file on google. I have found that a zero length /etc/lwresd.conf file was installed somehow on my linux.
In general, using "rndc" I am unable to prove that "lwresd" is working correctly and I suspect that the root cause of the issue is that the resolver libraries and lwresd.conf are not on the same page and that a properly configured lwresd.conf remedy this.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
resolv.conf is a very simple file. Basically an identification for the domain, and a list of DNS servers that can be queried:
--------------X8----------
nameserver 192.168.2.1
nameserver 194.72.9.34
nameserver 194.74.65.68
domain mydomain.co.uk
--------------X8----------
Amazingly enough, the above is also a valid lwresd.conf file. In fact, if the lwresd.conf file does not exist, then in many cases the lwresd will read the resolv.conf instead.
I personally haven't used any other commands for the lwresd, and the only fields that I can see are useful to the lwresd are the nameserver ones, as this daemon has no access to anything other than the DNS servers, and it's own cache of previously requested name/ip address pairs. It also omits any 'trusted' capability which could be used to update DNS servers....so I guess that the only commands that you need in your lwresd.conf file are the nameserver ones. I think that the lwresd *really* is that 'lightweight'!
--------------X8----------
nameserver 192.168.2.1
nameserver 194.72.9.34
nameserver 194.74.65.68
domain mydomain.co.uk
--------------X8----------
Amazingly enough, the above is also a valid lwresd.conf file. In fact, if the lwresd.conf file does not exist, then in many cases the lwresd will read the resolv.conf instead.
I personally haven't used any other commands for the lwresd, and the only fields that I can see are useful to the lwresd are the nameserver ones, as this daemon has no access to anything other than the DNS servers, and it's own cache of previously requested name/ip address pairs. It also omits any 'trusted' capability which could be used to update DNS servers....so I guess that the only commands that you need in your lwresd.conf file are the nameserver ones. I think that the lwresd *really* is that 'lightweight'!
ASKER