Folks, recently I've run in to 2 issues that I don't know how to solve.
I have a local dns server on my network. This has always worked and I've made no changes since July. Last week dns lookups from one of the systems on my network worked fine. Now they all fail.
dig truckin
results in
; <<>> DiG 9.18.28 <<>> truckin ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 53771 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;truckin. IN A
;; Query time: 4010 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP) ;; WHEN: Mon Sep 16 17:15:20 PDT 2024 ;; MSG SIZE rcvd: 36
All lookups return refused. All lookups on the server work fine. The server is F40 and the other system is F39. Both systems have been updated to the latest set of patches.
The other issue is logrotate. It no longer seems to run automatically as a daily cron job as it used to. Now in order to have the file in /var/log be rotated I have to run logrotate manually. A related issue is that logrotate wont rotate /var/log/boot.log due to the following:
rotating pattern: /var/log/boot.log after 1 days (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/boot.log log /var/log/boot.log has multiple (2) hard links. Rotation of files with multiple hard links is not allowed for /var/log/boot.log -- skipping.
In order to get it to work you need to add allowhardlink to the /etc/logrotate.d/bootlog file.
Any help is appreciated.
Paolo
On 17 Sep 2024, at 01:26, Paolo Galtieri pgaltieri@gmail.com wrote:
Folks, recently I've run in to 2 issues that I don't know how to solve.
I have a local dns server on my network. This has always worked and I've made no changes since July. Last week dns lookups from one of the systems on my network worked fine. Now they all fail.
dig truckin
results in
; <<>> DiG 9.18.28 <<>> truckin ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 53771 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;truckin. IN A
;; Query time: 4010 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP) ;; WHEN: Mon Sep 16 17:15:20 PDT 2024 ;; MSG SIZE rcvd: 36
All lookups return refused. All lookups on the server work fine. The server is F40 and the other system is F39. Both systems have been updated to the latest set of patches.
The other issue is logrotate. It no longer seems to run automatically as a daily cron job as it used to. Now in order to have the file in /var/log be rotated I have to run logrotate manually. A related issue is that logrotate wont rotate /var/log/boot.log due to the following:
rotating pattern: /var/log/boot.log after 1 days (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/boot.log log /var/log/boot.log has multiple (2) hard links. Rotation of files with multiple hard links is not allowed for /var/log/boot.log -- skipping.
In order to get it to work you need to add allowhardlink to the /etc/logrotate.d/bootlog file.
Any help is appreciated.
Where is the local DNS running? Is it the fedora server? If so what software are you using to provide DNS?
You might want to test with resolvectl query to see if that provides any insights.
Barry
Paolo
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Barry, I'm using bind and this has been working for years without issues until this week. The dns server is running on F40 and this system I have upgraded from F35 -> F36 -> F37 -> F38 -> F39 -? F40 without issues.
Of course as soon as report this issue and after installing today's updates it all works :-)
Paolo
On 9/16/24 23:50, Barry Scott wrote:
On 17 Sep 2024, at 01:26, Paolo Galtieri pgaltieri@gmail.com wrote:
Folks, recently I've run in to 2 issues that I don't know how to solve.
I have a local dns server on my network. This has always worked and I've made no changes since July. Last week dns lookups from one of the systems on my network worked fine. Now they all fail.
dig truckin
results in
; <<>> DiG 9.18.28 <<>> truckin ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 53771 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;truckin. IN A
;; Query time: 4010 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP) ;; WHEN: Mon Sep 16 17:15:20 PDT 2024 ;; MSG SIZE rcvd: 36
All lookups return refused. All lookups on the server work fine. The server is F40 and the other system is F39. Both systems have been updated to the latest set of patches.
The other issue is logrotate. It no longer seems to run automatically as a daily cron job as it used to. Now in order to have the file in /var/log be rotated I have to run logrotate manually. A related issue is that logrotate wont rotate /var/log/boot.log due to the following:
rotating pattern: /var/log/boot.log after 1 days (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/boot.log log /var/log/boot.log has multiple (2) hard links. Rotation of files with multiple hard links is not allowed for /var/log/boot.log -- skipping.
In order to get it to work you need to add allowhardlink to the /etc/logrotate.d/bootlog file.
Any help is appreciated.
Where is the local DNS running? Is it the fedora server? If so what software are you using to provide DNS?
You might want to test with resolvectl query to see if that provides any insights.
Barry
Paolo
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 17 Sep 2024, at 15:43, Paolo Galtieri pgaltieri@gmail.com wrote:
I'm using bind and this has been working for years without issues until this week. The dns server is running on F40 and this system I have upgraded from F35 -> F36 -> F37 -> F38 -> F39 -? F40 without issues.
Of course as soon as report this issue and after installing today's updates it all works :-)
I also use bind and have not seen an issue. Did bind update for you today which might explain the fix?
Barry
-
Barry -
Barry Scott
-
Paolo Galtieri