[DNG] resolv.conf
I do not know how long ago it was, but some of my mail started to go out without an envelop sender address. I've not yet been able to figure why, but one thing I don't like is the appearance of my /etc/resolv.conf file. It looks like this: nameserver 192.168.254.254 search home domain home The 192.1683.254.254 is my router. I assume that "home' is useless. I installed resolvcom, ran it with a -u option and rebooted. All this did was to remove the domain line from resolv.conf. How is resolv.conf supposed to get the name of my ISP? I suppose from my router. The router knows what Frontier SSID it is using and the connection type is DHCP via 802.1x. It says public LAN is disabled. But it appends -16 to my host name. My mail problem may have started when Frontier replaced my router. I installed resolvcon, ran it and rebooted. All it did was to remove the domain line. It used to be that for both the search and domian lines was found the name of my ISP (Frontier.com). This seemd to work. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] resolv.conf
On 5/8/22 07:45, Haines Brown wrote: I do not know how long ago it was, but some of my mail started to go out without an envelop sender address. I've not yet been able to figure why, but one thing I don't like is the appearance of my /etc/resolv.conf file. It looks like this: nameserver 192.168.254.254 search home domain home The 192.1683.254.254 is my router. I assume that "home' is useless. I installed resolvcom, ran it with a -u option and rebooted. All this did was to remove the domain line from resolv.conf. How is resolv.conf supposed to get the name of my ISP? I suppose from my router. The router knows what Frontier SSID it is using and the connection type is DHCP via 802.1x. It says public LAN is disabled. But it appends -16 to my host name. My mail problem may have started when Frontier replaced my router. I installed resolvcon, ran it and rebooted. All it did was to remove the domain line. It used to be that for both the search and domian lines was found the name of my ISP (Frontier.com). This seemd to work. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng Years ago I became fed up with too many applications and installations corrupting my resolv.conf. I type in a resolv.conf using an editor. domain billshome search billshome nameserver 10.0.0.252 My router knows about the domain (DD-WRT Linksys) and will promote an unresolved search to the WAN port as per BIND standards. To prevent the file from being corrupted by other applications: --> I keep a copy in /etc/src --> I check in the bind boot (init.d) script with diff and copy the src file if needs be. --> I look for any init scripts that toy with the file and alter them if possible. --> If you make the file a symbolic link, most scripts seem to ignore altering it. Hope this helps. OpenPGP_0xF8317D97BF4DA69A.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] resolv.conf
On Sunday 08 May 2022 at 16:24:03, william m. moss wrote: > Years ago I became fed up with too many applications and installations > corrupting my resolv.conf. I type in a resolv.conf using an editor. Me too. > To prevent the file from being corrupted by other applications: chattr +i /etc/resolv.conf Antony. -- "Microsoft's profit margins require a monopoly lock on the market; thus, they're stuck with being predatory evil bastards. The moment they stop being predatory evil bastards, their stock price will tank and their options pyramid will crash and it will be all over." - Eric S Raymond Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] resolv.conf
On Sun, 2022-05-08 at 10:24 -0400, william m. moss wrote: > > Years ago I became fed up with too many applications and > installations > corrupting my resolv.conf. I type in a resolv.conf using an editor. > > domain billshome > search billshome > nameserver 10.0.0.252 There is one big problem with having 'domain' and 'search' in /etc/resolv.conf , they are mutually exclusive and the last one wins, so that resolv.conf is actually: search billshome nameserver 10.0.0.252 I should also point out that a one word TLD isn't a good idea. Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] resolv.conf
If you don't have a public domain, then the correct domain to use in an internal networks is home.arpa, see: https://tools.ietf.org/id/draft-ietf-homenet-dot-07.html home.arpa. is intentionaly set up as an unsigned delegation, so it won't break when someone uses dnssec. Other domains will fail dnssec. Unfortunately, noone seams to ever check dnssec for some reason, and noone seams to care about home.arpa either. But I'm still optimistic that this may someday change. Regards, Daniel Abrecht ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] decode usenet messages
I currently use pan to read usenet. It works fine. Presumably it, and almost every decent newsreader, has components that * obtain a message from usenet * display it in various ways, including handling text, embedded images, and so forth. * other things too What I want now, however, is to see the contents of usenet messages that have already been downloaded -- years ago. In other words, I'd like to use the facilities that are already baked into every decent usenet reader to process a message that's already on my hard drive. (for example, one I've downloaded way back in 2004). But I don't want the everything else that makes that part of a huge, full-function usenet eader. But all the readers I've investigated seem willing to handle only messages they download themselves or have stored within their own on-disk data structures. There seems to be no mechanism for taking a usenet message obtained from elsewhere. I'm just trying to see messages I've already got, so I can decide whether they are worth keeping. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] decode usenet messages
On Sun, May 08, 2022 at 06:57:51PM -0400, Hendrik Boom wrote: > > What I want now, however, is to see the contents of usenet messages > that have already been downloaded -- years ago. In other words, I'd > like to use the facilities that are already baked into every decent > usenet reader to process a message that's already on my hard drive. > (for example, one I've downloaded way back in 2004). But I don't want > the everything else that makes that part of a huge, full-function > usenet eader. > > But all the readers I've investigated seem willing to handle only > messages they download themselves or have stored within their own > on-disk data structures. There seems to be no mechanism for taking a > usenet message obtained from elsewhere. > What you want is a (local) usenet server. Usenet is like e-mail with a clear division of labour between server and client. I can't advise about which server to use, it's been a long time I used one. Gyelt -- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
