I mentioned earlier that I was having trouble with a new dsl modem's behavior as a dns server. That has been resolved by avoiding dhcp. This was accomplished with the help of a visiting geek (my son). Resolveconf was installed; dns addresses set statically,
As best as I can determine, everything is working fine. But I seek some understanding. The resolv.conf contains some entries which make no sense to me. The visiting geek is no longer interested in these questions, as it is no longer broken. So I appeal to you. resolv.conf: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.0.1 nameserver 69.64.224.67 nameserver 69.64.224.66 search domain.actdsltmp I expect that the nameserver 192.168.0.1 entry is left over from earlier dhcp responses. (Visiting geek's Debian machine has only the two valid nameserver entries in his file--he had not run a dhcp client.) Why does it persist in this file? And why does it not break dns searches occasionally? If I run dig repeatedly, only the 69.64.224.67 address seems to get used. If I force use of 192.168.0.1, it fails, as expected. What does "search domain.actdsltmp" do? Is domain.actdsltmp a valid name? Should I attempt to clean up this file? If I should, how might that be done? Thanks for any education you can throw my way. -Denis _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
