Re: [CentOS] rsync upgrade
On 8/6/20 8:45 AM, J Martin Rushton via CentOS wrote: C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever. Is there a reason you think that? RHEL 7 was originally released with 3.0.9, so we can demonstrate that Red Hat will update not only revision, but minor version increases within an RHEL major release. RHEL 7's last minor release will be 7.9, later this year. It would surprise me if rsync were updated after that, but not terribly surprising if that release included an update. https://access.redhat.com/support/policy/updates/errata/#Maintenance_Support_2_Phase http://vault.centos.org/7.0.1406/os/Source/SPackages/ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Thunderbird 68.10.0
On 7/29/20 6:28 PM, Johnny Hughes wrote: > On 7/27/20 1:43 PM, Leon Fauster via CentOS wrote: >> Am 27.07.20 um 19:50 schrieb Chris Schanzle via CentOS: >>> Sorry if I'm being overly impatient, but is there some snag with >>> releasing Thunderbird 68.10.0 for EL8? >>> >>> [RHSA-2020:3038-01] Important: thunderbird security update >>> >>> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Faccess.redhat.com%2Ferrata%2FRHSA-2020%3A3038data=02%7C01%7Cchristopher.schanzle%40nist.gov%7C638e7edab7454c80ef2408d8340eb9d7%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C637316585150559834sdata=HkuReVjbdCYxkaehqjeC6oNlRBxKcZXIEbUDoKvJuJo%3Dreserved=0 >>> >>> Thanks! >>> >> at the door: >> >> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.centos.org%2Frpms%2Fthunderbird%2Freleasesdata=02%7C01%7Cchristopher.schanzle%40nist.gov%7C638e7edab7454c80ef2408d8340eb9d7%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C637316585150569829sdata=cywUwwoVucVxW6o9EQNDimm280PVFkRx%2BgF4SEGYkDA%3Dreserved=0 > We have been working non-stop for the last several days on the embargoed > kernel, grub2, and other secure boot items (that is .. the 'Boot Hole' > issue) for el7 and el8 for the .. therefore some other updates were > pushed back. > > I am trying to finish up the 'Boot Hole' el7 updates right now .. 2 > other people are currently working on the el8 items. > > Once these get pushed .. hopefully tonight .. we will be working on the > other updates starting tomorrow. > > Thanks, > Johnny Hughes First, thank you for all the efforts that went into the Boot Hole / shim issue. I'm sorry for the bad PR CentOS got for it. I do hope upstream will not have more occurrences of the like...historically, they've been very reliable, which is why it is my choice of OS. Just a friendly reminder Thunderbird 68.10 hasn't been released for CentOS 8. And I see RHEL has announced Thunderbird 68.11.0: https://access.redhat.com/errata/RHSA-2020:3341 I do hope the day will come where we can meet so I can thank you in person. It would be a great pleasure buy you a beer / meal / t-shirt. Best regards, Chris ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync upgrade
FYI, the IUS rsync31u package is going to be retired (unmaintained) in about a month. Upstream confirmed that there will never be another 3.1.x release. https://github.com/WayneD/rsync/issues/80 https://github.com/iusrepo/announce/issues/23 If there is still value in providing a newer rsync package for EL7 in IUS, I'd recommend requesting an rsync3 package (now that we know that upstream doesn't maintain old minor versions) on the wishlist. https://github.com/iusrepo/wishlist On Thu, Aug 6, 2020 at 6:11 PM John R. Dennison wrote: > > On Thu, Aug 06, 2020 at 10:40:14AM -0500, Christopher Wensink wrote: > > Can anyone tell me the repository to use to upgrade to a version of > > rsync later than 3.1.2? > > IUS has 3.1.3 for EL7. More information available via writeup at > https://wiki.centos.org/AdditionalResources/Repositories or > https://ius.io/ > > > > > > John > > -- > When a man tells you that he got rich through hard work, ask him: "Whose?" > > -- Don Marquis (1878-1937), American humorist, journalist, and author > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos -- Carl George ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync upgrade
I have not built my own RPMs before, just built from source .tar.gz files, do you have a good tutorial? Is a package built by you inherently more secure than a package strait from a mirror? On 8/6/2020 8:12 PM, Chris Schanzle via CentOS wrote: > On 8/6/20 12:30 PM, Jack Bailey via CentOS wrote: >> On 2020-08-06 08:45, J Martin Rushton via CentOS wrote: >>> You'll need to upgrade to CentOS8. >>> >>> C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever. >>> >>> C8.2 is at 3.1.3-7, C8 will always be on 3.1.3 >>> >>> Martin >> Another option is to build rsync from source, which is what I did to try out >> the zstd compression. > > Just wanted to share Fedora 32's rsync-3.2.2-1.fc32.src.rpm rebuilds cleanly > without any necessary tweaks on CentOS 7. I used mock for a clean build > environment. > > It is very empowering to learn how to build your own packages and not very > hard to get started. I encourage you to do the same! > > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Christopher Wensink IS Administrator Five Star Plastics, Inc 1339 Continental Drive Eau Claire, WI 54701 Office: 715-831-1682 Mobile: 715-563-3112 Fax: 715-831-6075 cwens...@five-star-plastics.com www.five-star-plastics.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync upgrade
On 8/6/20 12:30 PM, Jack Bailey via CentOS wrote: > On 2020-08-06 08:45, J Martin Rushton via CentOS wrote: >> You'll need to upgrade to CentOS8. >> >> C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever. >> >> C8.2 is at 3.1.3-7, C8 will always be on 3.1.3 >> >> Martin > > Another option is to build rsync from source, which is what I did to try out > the zstd compression. Just wanted to share Fedora 32's rsync-3.2.2-1.fc32.src.rpm rebuilds cleanly without any necessary tweaks on CentOS 7. I used mock for a clean build environment. It is very empowering to learn how to build your own packages and not very hard to get started. I encourage you to do the same! ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync upgrade
I used that one, and it fixed the issue with the synology backup. 4 hrs 12 min into the backup and 1.5 TB backed up. Thanks everyone! On 8/6/2020 6:11 PM, John R. Dennison wrote: > On Thu, Aug 06, 2020 at 10:40:14AM -0500, Christopher Wensink wrote: >> Can anyone tell me the repository to use to upgrade to a version of >> rsync later than 3.1.2? > IUS has 3.1.3 for EL7. More information available via writeup at > https://wiki.centos.org/AdditionalResources/Repositories or > https://ius.io/ > > > > > > John > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos -- Christopher Wensink IS Administrator Five Star Plastics, Inc 1339 Continental Drive Eau Claire, WI 54701 Office: 715-831-1682 Mobile: 715-563-3112 Fax: 715-831-6075 cwens...@five-star-plastics.com www.five-star-plastics.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync upgrade
On Thu, Aug 06, 2020 at 10:40:14AM -0500, Christopher Wensink wrote: > Can anyone tell me the repository to use to upgrade to a version of > rsync later than 3.1.2? IUS has 3.1.3 for EL7. More information available via writeup at https://wiki.centos.org/AdditionalResources/Repositories or https://ius.io/ John -- When a man tells you that he got rich through hard work, ask him: "Whose?" -- Don Marquis (1878-1937), American humorist, journalist, and author pgpRXZcw1fkSz.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync upgrade
Am 06.08.20 um 21:10 schrieb Phil Perry: On 06/08/2020 17:30, Jack Bailey via CentOS wrote: On 2020-08-06 08:45, J Martin Rushton via CentOS wrote: You'll need to upgrade to CentOS8. C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever. C8.2 is at 3.1.3-7, C8 will always be on 3.1.3 Martin Another option is to build rsync from source, which is what I did to try out the zstd compression. Or you could try rebuilding the latest fedora SRPM on el7 (or the RHEL8 SRPM if that is new enough for you). Sometimes it's straight forward, other times this approach may fail with newer build requirements than those provided by el7. Worth a try though. or https://rsync.samba.org/download.html#Binaries https://download.samba.org/pub/rsync/binaries/centos-7.8-x86_64/ or asking upstream to upgrade: https://bugzilla.redhat.com or As they always say to me: "If this issue is critical or in any way time sensitive, please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution. For information on how to contact the Red Hat production support team, please visit: https://access.redhat.com/support; As "Hick's law" say https://en.wikipedia.org/wiki/Hick's_law -- After the boot hole scream in the funny mode now, Leon :) ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync upgrade
The problem that I keep running into is, our synology backup device (RS3618xs) has an option to make a connection to each Linux VM, and our file server's backup keeps failing every night with the error message: "The samba shared folder settings of the source data cannot support backup. Please disable "store dos attributes" and "vss objects". In smb.conf the only reference to store dos attributes is a commented out line, and nothing references vss objects. This error is coming up on a new vm running Centos 7.8.2003 (Core), Samba 4.10.4, rsync 3.1.2. The exact same setup on the old vm running Centos6.10 (Final), Samba 3.6.23-53.el6_10, rsync 3.0.6 with the same files which have DOS attributes on them, and the backup works fine. Other VM's running the same command structure using the same version of Centos 7 work without issues. Per Synology support the issue is the files that contain DOS attributes are breaking the backup. Is anyone aware of issues with files that contain DOS attributes breaking rsync backups on Centos7.8.2003 with Samba 4.10.4 and Rsync 3.1.2? Chris On 8/6/2020 2:10 PM, Phil Perry wrote: > On 06/08/2020 17:30, Jack Bailey via CentOS wrote: >> On 2020-08-06 08:45, J Martin Rushton via CentOS wrote: >>> You'll need to upgrade to CentOS8. >>> >>> C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever. >>> >>> C8.2 is at 3.1.3-7, C8 will always be on 3.1.3 >>> >>> Martin >> >> Another option is to build rsync from source, which is what I did to >> try out the zstd compression. >> > > Or you could try rebuilding the latest fedora SRPM on el7 (or the > RHEL8 SRPM if that is new enough for you). Sometimes it's straight > forward, other times this approach may fail with newer build > requirements than those provided by el7. > > Worth a try though. > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos -- Christopher Wensink IS Administrator Five Star Plastics, Inc 1339 Continental Drive Eau Claire, WI 54701 Office: 715-831-1682 Mobile: 715-563-3112 Fax: 715-831-6075 cwens...@five-star-plastics.com www.five-star-plastics.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync upgrade
On 06/08/2020 17:30, Jack Bailey via CentOS wrote: On 2020-08-06 08:45, J Martin Rushton via CentOS wrote: You'll need to upgrade to CentOS8. C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever. C8.2 is at 3.1.3-7, C8 will always be on 3.1.3 Martin Another option is to build rsync from source, which is what I did to try out the zstd compression. Or you could try rebuilding the latest fedora SRPM on el7 (or the RHEL8 SRPM if that is new enough for you). Sometimes it's straight forward, other times this approach may fail with newer build requirements than those provided by el7. Worth a try though. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixing grub/shim issue Centos 7
Le 06/08/2020 à 16:53, Kenneth Porter a écrit : > A practical equivalent is simply to avoid applying updates for a week to see > if > someone else gets burned by them. I'm already waiting for a weekend so I don't > disrupt work in case a catastrophe happens, and I wait at least a week and > watch this list for any reports of disaster. So I haven't experienced this > one. > Let the impatient do your testing for you. So a zero-day becomes at least an eight-day. :o) -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync upgrade
On 2020-08-06 08:45, J Martin Rushton via CentOS wrote: You'll need to upgrade to CentOS8. C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever. C8.2 is at 3.1.3-7, C8 will always be on 3.1.3 Martin Another option is to build rsync from source, which is what I did to try out the zstd compression. centos7$ rsync --version rsync version 3.2.2 protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, atimes, batchfiles, inplace, append, no ACLs, xattrs, optional protect-args, iconv, symtimes, prealloc Optimizations: no SIMD, asm, openssl-crypto Checksum list: xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none On 06/08/2020 16:40, Christopher Wensink wrote: Can anyone tell me the repository to use to upgrade to a version of rsync later than 3.1.2? Chris ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsync upgrade
You'll need to upgrade to CentOS8. C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever. C8.2 is at 3.1.3-7, C8 will always be on 3.1.3 Martin On 06/08/2020 16:40, Christopher Wensink wrote: Can anyone tell me the repository to use to upgrade to a version of rsync later than 3.1.2? Chris -- J Martin Rushton MBCS ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] rsync upgrade
Can anyone tell me the repository to use to upgrade to a version of rsync later than 3.1.2? Chris -- Christopher Wensink IS Administrator Five Star Plastics, Inc 1339 Continental Drive Eau Claire, WI 54701 Office: 715-831-1682 Mobile: 715-563-3112 Fax: 715-831-6075 cwens...@five-star-plastics.com www.five-star-plastics.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixing grub/shim issue Centos 7
On Thu, Aug 06, 2020 at 03:57:56PM +0200, Nicolas Kovacs wrote: > Le 04/08/2020 à 08:31, lpeci a écrit : > > I had the same problem with my UEFI bios machine and I fixed it so for > > Centos 7: While this worked for me, it might not work for you... My "solution" was to boot the previous kernel, which came up just fine, yum remove kernel.xx.yy.zz yum install kernel.xx.yy.zz which rebuilds the initrd, and voila! Fred > > > > 1) Boot from an rescue linux usb > > > > 2) When the rescue system is running: > > > > 2.1) #chroot /mnt/sysimage > > > > 3) Config network: > > > > 3.1) # ip addr add X.X.X.X/X dev X > > > > 3.2) # ip route add default via X.X.X.X <--- default router > > > > 4) And finally: > > > > #yum downgrade shim\* grub2\* mokutil > > > > #exit > > > > #reboot > > > > I hope you can fix it with these steps. > > Thanks for the detailed suggestion. > > Unfortunately I couldn't recover the installation, and I had to redo > everything > from scratch, which cost me the first two days of my holidays. > > One thought regularly kept crossing my mind: > > "How on earth could this have passed Q & A ?" > > :o) > > Cheers, > > Niki > > -- > Microlinux - Solutions informatiques durables > 7, place de l'église - 30730 Montpezat > Site : https://www.microlinux.fr > Blog : https://blog.microlinux.fr > Mail : i...@microlinux.fr > Tél. : 04 66 63 10 32 > Mob. : 06 51 80 12 12 > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos -- Fred Smith -- fre...@fcshome.stoneham.ma.us - The eyes of the Lord are everywhere, keeping watch on the wicked and the good. - Proverbs 15:3 (niv) - ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixing grub/shim issue Centos 7
On 8/6/2020 7:25 AM, Simon Matter via CentOS wrote: The only real solution I can think of to prevent this would be to make preview versions of updates available to the public so that a lot of people can test them on their hardware, hopefully spare hardware, and give feedback. A practical equivalent is simply to avoid applying updates for a week to see if someone else gets burned by them. I'm already waiting for a weekend so I don't disrupt work in case a catastrophe happens, and I wait at least a week and watch this list for any reports of disaster. So I haven't experienced this one. Let the impatient do your testing for you. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixing grub/shim issue Centos 7
> Le 04/08/2020 à 08:31, lpeci a écrit : >> I had the same problem with my UEFI bios machine and I fixed it so for >> Centos 7: >> >> 1) Boot from an rescue linux usb >> >> 2) When the rescue system is running: >> >> 2.1) #chroot /mnt/sysimage >> >> 3) Config network: >> >> 3.1) # ip addr add X.X.X.X/X dev X >> >> 3.2) # ip route add default via X.X.X.X <--- default router >> >> 4) And finally: >> >> #yum downgrade shim\* grub2\* mokutil >> >> #exit >> >> #reboot >> >> I hope you can fix it with these steps. > > Thanks for the detailed suggestion. > > Unfortunately I couldn't recover the installation, and I had to redo > everything > from scratch, which cost me the first two days of my holidays. Now you know how the Window$ admins suffered all the years :-) > > One thought regularly kept crossing my mind: > > "How on earth could this have passed Q & A ?" Quite simple I guess. It's one of the cases where you can not test so easily like other updates. Here you have to make tests on real hardware, different hardware of all kind and can not do it in the Cloud, a VM or whatever. The only real solution I can think of to prevent this would be to make preview versions of updates available to the public so that a lot of people can test them on their hardware, hopefully spare hardware, and give feedback. I think current business models do not support such a way these days. However one can find strategies to survive. What I do is: * Never update any system directly from what is provided online. Sync to local repositories first to control what is fed to your systems. * Never blindly apply updates. Always do tests on not so important systems or dedicated test systems first. * If all goes well, update important systems. If you have multiple systems, update only one first as another test. Then update others. I have learned my lessons in the past decades but this was a good wake up call to follow above rules even more strictly. Better safe than sorry. Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fixing grub/shim issue Centos 7
Le 04/08/2020 à 08:31, lpeci a écrit : > I had the same problem with my UEFI bios machine and I fixed it so for Centos > 7: > > 1) Boot from an rescue linux usb > > 2) When the rescue system is running: > > 2.1) #chroot /mnt/sysimage > > 3) Config network: > > 3.1) # ip addr add X.X.X.X/X dev X > > 3.2) # ip route add default via X.X.X.X <--- default router > > 4) And finally: > > #yum downgrade shim\* grub2\* mokutil > > #exit > > #reboot > > I hope you can fix it with these steps. Thanks for the detailed suggestion. Unfortunately I couldn't recover the installation, and I had to redo everything from scratch, which cost me the first two days of my holidays. One thought regularly kept crossing my mind: "How on earth could this have passed Q & A ?" :o) Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7 shim fix failed
On 8/5/20 5:40 AM, Kenneth Porter wrote: Is there some way we could get the initrd rebuild to be more verbose, so that it doesn't appear to hang? It would be nice to get feedback that something is happening, especially on an older, slower system that takes a long time for this step. While the process CAN be made more verbose, it won't help any. RPM scriptlets are actually not supposed to generate output; both rpm and yum (and by extension dnf) buffer scriptlet output so that any messages that are issued will all be seen after the entire scriptlet has run. The same thing is true for say the ELrepo kmods, such as kmod-nvidia. That rpm needs to rebuild the initrd, and even issues a message saying something like 'this may take a while' or similar, but you won't get that message until the scriptlet doing the initrd rebuild has finished. This is one area I think the Debian packaging system is a bit superior, in that dpkg's can issue progress reports and similar. But rpm has been this way for a really really long time, ever since I maintained the PostgreSQL RPMset from 1999 to 2004. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 DNS resolution not working as expected
Pete Biggs writes: > > > > man host > > > > > >-N ndots > > >The number of dots that have to be in name for it to be > > > considered absolute. The default value is that defined using > > >the ndots statement in /etc/resolv.conf, or 1 if no ndots > > > statement is present. Names with fewer dots are interpreted > > >as relative names and will be searched for in the domains > > > listed in the search or domain directive in > > >/etc/resolv.conf. > > > > As per man resolv.conf, the default setting hasn't changed. It is n=1 on > > all of CentOS 6/7/8. > > > > Does > >host -N2 foo.subdomain > > work on CentOS 8? Does it work if you put ndots: 2 in resolv.conf? > > There may have been a change in behaviour - from the tests I've done it > seems more like it's fixing a bug/inconsistency somewhere because doing > >host -N1 foo.subdomain > > should not work, but it does on CentOS 7. Interesting. Yes, host -N2 works, as does ndots:2. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 DNS resolution not working as expected
> > man host > > > >-N ndots > >The number of dots that have to be in name for it to be > > considered absolute. The default value is that defined using > >the ndots statement in /etc/resolv.conf, or 1 if no ndots > > statement is present. Names with fewer dots are interpreted > >as relative names and will be searched for in the domains listed > > in the search or domain directive in > >/etc/resolv.conf. > > As per man resolv.conf, the default setting hasn't changed. It is n=1 on all > of CentOS 6/7/8. > Does host -N2 foo.subdomain work on CentOS 8? Does it work if you put ndots: 2 in resolv.conf? There may have been a change in behaviour - from the tests I've done it seems more like it's fixing a bug/inconsistency somewhere because doing host -N1 foo.subdomain should not work, but it does on CentOS 7. P. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 DNS resolution not working as expected
I also, don't see a search stanza. Best Regards, Strahil Nikolov На 6 август 2020 г. 13:30:13 GMT+03:00, isdtor написа: >Pete Biggs writes: >> On Thu, 2020-08-06 at 10:26 +0100, isdtor wrote: >> > [root@localhost ~]# lsb_release -d >> > Description: CentOS Linux release 8.2.2004 (Core) >> > [root@localhost ~]# cat /etc/resolv.conf >> > # Generated by NetworkManager >> > search subdomain.company.com company.com >> > nameserver 1.2.3.4 >> > nameserver 5.6.7.8 >> > >> > [root@localhost ~]# host foo >> > foo.subdomain.company.com has address 1.2.3.4 >> > >> > [root@localhost ~]# host foo.subdomain >> > Host foo.subdomain not found: 3(NXDOMAIN) >> > >> > [root@localhost ~]# host foo.subdomain.company.com >> > foo.subdomain.company.com has address 1.2.3.4 >> > [root@localhost ~]# >> > >> > The expected result is that the lookup for foo.subdomain works, >like it does under CentOS < 8. >> >> man host >> >>-N ndots >>The number of dots that have to be in name for it to be >considered absolute. The default value is that defined using >>the ndots statement in /etc/resolv.conf, or 1 if no ndots >statement is present. Names with fewer dots are interpreted >>as relative names and will be searched for in the domains >listed in the search or domain directive in >>/etc/resolv.conf. > >As per man resolv.conf, the default setting hasn't changed. It is n=1 >on all of CentOS 6/7/8. > >___ >CentOS mailing list >CentOS@centos.org >https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 DNS resolution not working as expected
Pete Biggs writes: > On Thu, 2020-08-06 at 10:26 +0100, isdtor wrote: > > [root@localhost ~]# lsb_release -d > > Description:CentOS Linux release 8.2.2004 (Core) > > [root@localhost ~]# cat /etc/resolv.conf > > # Generated by NetworkManager > > search subdomain.company.com company.com > > nameserver 1.2.3.4 > > nameserver 5.6.7.8 > > > > [root@localhost ~]# host foo > > foo.subdomain.company.com has address 1.2.3.4 > > > > [root@localhost ~]# host foo.subdomain > > Host foo.subdomain not found: 3(NXDOMAIN) > > > > [root@localhost ~]# host foo.subdomain.company.com > > foo.subdomain.company.com has address 1.2.3.4 > > [root@localhost ~]# > > > > The expected result is that the lookup for foo.subdomain works, like it > > does under CentOS < 8. > > man host > >-N ndots >The number of dots that have to be in name for it to be considered > absolute. The default value is that defined using >the ndots statement in /etc/resolv.conf, or 1 if no ndots > statement is present. Names with fewer dots are interpreted >as relative names and will be searched for in the domains listed > in the search or domain directive in >/etc/resolv.conf. As per man resolv.conf, the default setting hasn't changed. It is n=1 on all of CentOS 6/7/8. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 DNS resolution not working as expected
On Thu, 2020-08-06 at 10:26 +0100, isdtor wrote: > [root@localhost ~]# lsb_release -d > Description: CentOS Linux release 8.2.2004 (Core) > [root@localhost ~]# cat /etc/resolv.conf > # Generated by NetworkManager > search subdomain.company.com company.com > nameserver 1.2.3.4 > nameserver 5.6.7.8 > > [root@localhost ~]# host foo > foo.subdomain.company.com has address 1.2.3.4 > > [root@localhost ~]# host foo.subdomain > Host foo.subdomain not found: 3(NXDOMAIN) > > [root@localhost ~]# host foo.subdomain.company.com > foo.subdomain.company.com has address 1.2.3.4 > [root@localhost ~]# > > The expected result is that the lookup for foo.subdomain works, like it does > under CentOS < 8. man host -N ndots The number of dots that have to be in name for it to be considered absolute. The default value is that defined using the ndots statement in /etc/resolv.conf, or 1 if no ndots statement is present. Names with fewer dots are interpreted as relative names and will be searched for in the domains listed in the search or domain directive in /etc/resolv.conf. P. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 8 DNS resolution not working as expected
[root@localhost ~]# lsb_release -d Description:CentOS Linux release 8.2.2004 (Core) [root@localhost ~]# cat /etc/resolv.conf # Generated by NetworkManager search subdomain.company.com company.com nameserver 1.2.3.4 nameserver 5.6.7.8 [root@localhost ~]# host foo foo.subdomain.company.com has address 1.2.3.4 [root@localhost ~]# host foo.subdomain Host foo.subdomain not found: 3(NXDOMAIN) [root@localhost ~]# host foo.subdomain.company.com foo.subdomain.company.com has address 1.2.3.4 [root@localhost ~]# The expected result is that the lookup for foo.subdomain works, like it does under CentOS < 8. I tested this also on a RHEL8 machine and followed https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/manually-configuring-the-etc-resolv-conf-file_configuring-and-managing-networking to disable DNS processing by NM, but this did not change the outcome. How can the pre-CentOS 8 behaviour be restored? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
