BALUG-Admin

balug-admin@lists.balug.org

1 participants
540 discussions

list acceptance/moderation and balug-announc@lists.balug.org hold --> discard for most users
by Michael Paoli 07 Sep '24

07 Sep '24

One thing I do like about Mailman 3 is all the available message acceptance settings, both for list default, and per user. Those include: List default -- follow the list's default member action. Hold -- This holds the message for approval by the list moderators. Reject -- this automatically rejects the message by sending a bounce notice to the post's author. The text of the bounce notice can be configured by you. Discard -- this simply discards the message, with no notice sent to the post's author. Accept -- accepts any postings without any further checks. Default Processing -- run additional checks and accept the message. Most notably - Discard highly useful to set non-members to Discard. Likewise for moderated list(s) where few are allowed to post (e.g. balug-announce(a)lists.balug.org). Makes listadmin life fair bit easier, as most all such posting attempts, that would otherwise be held for moderation on Mailman 2, can be simply discarded, as almost all of them are junk/garbage/spam and the like - maybe only about once a year or so does a legitimate message come in that way. And Reject really isn't that useful, as that happens after the email has already been received, rather than at SMTP time, so there would be backscatter issues with that (the overwhelming number of such mail is spam, and those are typically rather to quite forged senders, victim compromised accounts, etc.). And ... not sure exactly how much I (dis)like it on Mailman 3, but Mailman 2 data was mostly in python 2 pickle (.pck) format files, with data/configuration bits also being in flat (and also html) files. Well, Mailman 3, while some configuration bits are stored in flat configuration files, for better and/or worse, most of the data is stored in an actual relatively proper database (e.g. sqlite). So, balug-announce(a)lists.balug.org e.g. imported from Mailman 2, most all users had the moderation set to hold (Mailman 2 didn't have a discard option). On Mailman 3 I set the list default to discard for that list. But almost all users were imported from Mailman 2 and that import preserved their hold setting. I wanted to change it for those users to the list default (discard). A bit to chase it down in the database, but once found and reasonably tested, one SQL statement to do the needed: UPDATE member SET moderation_action = NULL WHERE list_id = 'balug-announce.lists.balug.org' and moderation_action = 0; ... and with that done for 492 users. Yay!(?) Not super easy/pleasant but ... well, compared to Mailman 2, yeah I think it's at least fair bit better than Mailman 2, at least on that point/feature/capability.

1 0

balug.org domain renewed, now expires 2025-09-22T04:00:00Z
by Michael Paoli 02 Sep '24

02 Sep '24

balug.org domain renewed $ whois balug.org 2>&1 | fgrep -i expir Registry Expiry Date: 2025-09-22T04:00:00Z $

1 0

BALUG: Lists, stats, etc.
by Michael Paoli 01 Sep '24

01 Sep '24

dates, lists, number of members: YYYY-MM-DD announce talk admin 2024-08-01 497 232 32 2024-07-01 497 232 32 2024-06-01 498 231 33 2024-05-01 499 231 33 2024-04-01 500 230 33 2024-03-01 498 230 33 2024-02-01 499 229 33 2024-01-01 497 227 31 2023-12-01 497 227 32 2023-11-01 496 249 32 2023-10-01 496 248 32 2023-09-01 497 248 32 2023-08-01 498 248 32 2023-07-01 500 248 32 2023-06-01 501 249 32 2023-05-01 501 249 32 2023-04-01 501 249 32 2023-03-01 501 249 32 2023-02-01 501 249 32 2023-01-01 500 249 32 2022-12-01 520 249 32 2022-11-01 564 249 32 2022-10-01 589 249 32 2022-09-01 589 249 33 2022-08-01 616 249 33 2022-07-01 834 260 35 2022-06-01 832 259 35 2022-05-01 832 259 35 2022-04-01 832 259 35 2022-03-01 833 259 35 2022-02-01 833 259 35 2022-01-01 833 258 35 2021-12-01 832 257 35 2021-11-01 831 257 35 2021-10-01 832 257 35 2021-09-01 832 257 35 2021-08-01 832 257 35 2021-07-01 832 257 35 2021-06-01 832 256 35 2021-05-01 833 257 35 2021-04-01 832 259 35 2021-03-01 833 259 35 2021-02-01 833 259 35 2021-01-01 833 259 35 2020-12-01 832 259 35 2020-11-01 833 260 35 2020-10-01 834 260 35 2020-09-01 835 260 35 2020-08-01 834 259 34 2020-07-01 834 266 34 2020-06-01 838 266 34 2020-05-01 839 267 34 2020-04-01 840 270 34 2020-03-01 840 271 34 2020-02-01 841 271 34 2020-01-01 841 271 34 2019-12-01 841 271 34 2019-11-01 840 271 34 2019-10-01 842 271 34 2019-09-01 844 272 34 2019-08-01 847 272 34 2019-07-01 852 272 36 2019-06-01 854 273 37 2019-05-01 856 272 38 2019-04-01 853 273 38 2019-03-01 851 273 38 2019-02-01 853 273 38 2019-01-01 856 274 38 2018-12-01 858 274 38 2018-11-01 861 274 39 2018-10-02 862 274 39 2018-09-01 864 274 38 2018-07-28 866 278 38 2018-06-08 870 282 38 2018-04-28 875 282 38 2018-02-17 880 283 36 2017-11-04 883 284 36 2017-08-19 897 293 37 2017-07-01 897 297 38 2017-05-27 897 297 38 2017-05-16 897 296 38 2017-04-01 896 297 38 2017-03-30 885 297 38 2016-05-03 886 291 39 2016-04-03 887 290 39 2016-03-05 888 291 45 2016-01-05 887 295 45 2015-12-05 887 296 45 2015-11-07 887 301 45 2015-10-06 888 301 45 2015-09-05 887 301 45 2015-08-04 888 301 45 2015-07-03 888 300 45 2015-06-05 888 301 46 2015-05-02 885 298 45 2015-04-04 884 297 44 2015-03-07 886 298 44 2015-02-06 885 303 44 2015-01-07 885 304 45 2014-12-06 886 304 45 2014-11-01 884 302 45 2014-10-04 881 303 46 2014-09-06 878 309 44 2014-06-13 875 307 44 2014-05-02 874 306 44 2014-04-04 876 306 44 2014-03-01 876 306 43 2014-01-11 872 305 42 2013-10-05 854 293 40 2013-08-31 855 295 41 2013-07-20 852 297 40 2013-04-10 838 286 41 2013-03-03 841 289 41 2013-02-02 843 291 41 2012-12-15 845 310 41 2012-03-23 818 310 39 2012-02-01 813 307 40 2011-04-28 768 291 37 2011-02-27 762 288 36 2010-05-02 730 289 34 2010-04-01 727 291 33 2010-03-16 727 293 33 2009-12-16 716 290 33 2009-09-09 700 288 32 2009-03-27 677 287 29 2009-01-10 662 290 30 2008-08-17 635 290 29 2008-03-03 571 247 28 2008-01-02 337 260 28 2007-12-28 336 261 28 2007-09-03 264 258 27 2007-07-24 287 256 27 2007-06-17 280 249 27 references: http://www.balug.org/#Lists

1 0

BALUG: Lists, stats, etc.
by Michael Paoli 01 Aug '24

01 Aug '24

1 0

Fwd: Mailman 3 listadmin testing (and potential hosting) available
by Michael Paoli 16 Jul '24

16 Jul '24

FYI, did send this out: ---------- Forwarded message --------- From: Michael Paoli <michael.paoli(a)berkeley.edu> Date: Mon, Jul 15, 2024 at 11:54 PM Subject: Mailman 3 listadmin testing (and potential hosting) available To: Grant Bowman <grantbow(a)gmail.com>, Grant Bowman <grantbow(a)dvlug.org>, Aaron <acohen36(a)gmail.com>, Tom <tomrlopes(a)gmail.com>, Ian <droid1836(a)gmail.com>, Rick Moen <rick(a)linuxmafia.com>, Al <aw009(a)sunnyside.com> Various SF Bay Area [L]UG(s) [potential] list admin folk(s), May potentially be some additional folks (if interested, contact me). Thought I'd invite, for possible testing, etc. some folks that are list admins of various SF Bay Area [L]UG(s), or might be potentially very seriously interested in that. Most notably, have Mailman 3 fairly well set up (at least metastable) on the BALUG VM (still have more Mailman 2 --> Mailman 3 migration steps to fully test out and validate before I do all those migrations for the production lists, including related infrastructure of automation and information, etc.). In those regards, if folks are interested in a test list on there for potentially testing for [L]UG use and list administration thereof, just let me know. Note that there are test list(s) there currently (notably balug-test3(a)lists.balug.org which is on Mailman 3 and will eventually become and be merged into balug-test(a)lists.balug.org when that gets migrated to Mailman 3), but I was thinking more significantly and distinct from that, list(s) where I could grant folks full listadmin access and control. E.g.: sf-lug-test(a)lists.balug.org dvlug-test(a)lists.balug.org berkeleylug-test(a)lists.balug.org etc. Could even do different (sub)domains, e.g.: @lists.dvlug.org @lists.sf-lug.org etc., though subdomains would require some fair bit of additional work/coordination to set that all up properly (DNS, SPF, TLS, ...) so @lists.balug.org would be the simpler easier place to start and is already available. Anyway, if interested, let me know (and notably list name). If you merely want to test list, can use the existing balug-test3(a)lists.balug.org e.g. send email to: balug-test3-subscribe(a)lists.balug.org to subscribe or see: https://lists.balug.org/mailman3/postorius/lists/balug-test3.lists.balug.or… And yes, for at least many (SF [L]UG lists), I'd be willing to host on the BALUG VM (and in general they could have their own subdomain, in fact for actual general production use that would be exceedingly recommended, e.g. something like, say for SF-LUG: sf-lug(a)lists.sf-lug.org sf-lug-test(a)lists.sf-lug.org) But even if one mostly wants to reasonably well test out Mailman 3 and list administration thereof, the BALUG VM may be a useful place to be able to reasonably well do that (want to test drive Mailman 3 and see if it might make suitable list infrastructure for your [L]UG?). > From: Michael Paoli <michael.paoli(a)berkeley.edu> > Date: Sat, Jun 29, 2024 at 1:52 PM > Subject: Re: dvlug list > To: Grant Bowman <grantbow(a)gmail.com> > Cc: Diablo Valley Linux Users Group (DVLUG) <dvlug(a)linuxmafia.com>, > Diablo Valley Linux Users Group (DVLUG) <list(a)dvlug.org> > > Grant, ... > Oh, ... I'll also hang it out there for your consideration, if you > may be interested ... if you may possibly want to have subdomain with > DVLUG list(s) on <whatever>@lists.dvlug.org., I could potentially > host that if you so wanted that ... but maybe ask me again in a > couple weeks or so ... I'm still doing migration off of mailman > version 2 (could do mailman 2 in the meantime if you really wanted > that), so still have more testing, etc. to do, and want to wait a bit > 'till that's all done and the dust well settled before I consider > that migration to be a full success (in case I find any latent issues > that may not be immediately apparent). I'd also think Rick might > even be willing to do same (notably subdomain part for list) on the > existing linuxmafia.com host. In any case, food for thought. Could > also potentially migrate so all the old (most notably archives) would > still also be present under lists.dvlug.org (similar to how things > are for BALUG under lists.balug.org). Anyway, just a thought, and > thought I'd hang the offer out there if you may be interested (and > would also have the capability to access and back up full archives, > also member subscription list). And, yeah just to think about it > more generally, if you use a subdomain (e.g. lists.dvlug.org) for > list(s), rather than the main domain (dvlug.org), that does leave > things much more flexible for how one may want to handle list(s), > most notably it can be hosted or the like, exceedingly independent of > whatever else may be going on for hosting or whatever on > [www.]dvlug.org (e.g. web site, etc.).

1 0

BALUG: Lists, stats, etc.
by Michael Paoli 01 Jul '24

01 Jul '24

dates, lists, number of members: YYYY-MM-DD announce talk admin 2024-07-01 497 232 32 2024-06-01 498 231 33 2024-05-01 499 231 33 2024-04-01 500 230 33 2024-03-01 498 230 33 2024-02-01 499 229 33 2024-01-01 497 227 31 2023-12-01 497 227 32 2023-11-01 496 249 32 2023-10-01 496 248 32 2023-09-01 497 248 32 2023-08-01 498 248 32 2023-07-01 500 248 32 2023-06-01 501 249 32 2023-05-01 501 249 32 2023-04-01 501 249 32 2023-03-01 501 249 32 2023-02-01 501 249 32 2023-01-01 500 249 32 2022-12-01 520 249 32 2022-11-01 564 249 32 2022-10-01 589 249 32 2022-09-01 589 249 33 2022-08-01 616 249 33 2022-07-01 834 260 35 2022-06-01 832 259 35 2022-05-01 832 259 35 2022-04-01 832 259 35 2022-03-01 833 259 35 2022-02-01 833 259 35 2022-01-01 833 258 35 2021-12-01 832 257 35 2021-11-01 831 257 35 2021-10-01 832 257 35 2021-09-01 832 257 35 2021-08-01 832 257 35 2021-07-01 832 257 35 2021-06-01 832 256 35 2021-05-01 833 257 35 2021-04-01 832 259 35 2021-03-01 833 259 35 2021-02-01 833 259 35 2021-01-01 833 259 35 2020-12-01 832 259 35 2020-11-01 833 260 35 2020-10-01 834 260 35 2020-09-01 835 260 35 2020-08-01 834 259 34 2020-07-01 834 266 34 2020-06-01 838 266 34 2020-05-01 839 267 34 2020-04-01 840 270 34 2020-03-01 840 271 34 2020-02-01 841 271 34 2020-01-01 841 271 34 2019-12-01 841 271 34 2019-11-01 840 271 34 2019-10-01 842 271 34 2019-09-01 844 272 34 2019-08-01 847 272 34 2019-07-01 852 272 36 2019-06-01 854 273 37 2019-05-01 856 272 38 2019-04-01 853 273 38 2019-03-01 851 273 38 2019-02-01 853 273 38 2019-01-01 856 274 38 2018-12-01 858 274 38 2018-11-01 861 274 39 2018-10-02 862 274 39 2018-09-01 864 274 38 2018-07-28 866 278 38 2018-06-08 870 282 38 2018-04-28 875 282 38 2018-02-17 880 283 36 2017-11-04 883 284 36 2017-08-19 897 293 37 2017-07-01 897 297 38 2017-05-27 897 297 38 2017-05-16 897 296 38 2017-04-01 896 297 38 2017-03-30 885 297 38 2016-05-03 886 291 39 2016-04-03 887 290 39 2016-03-05 888 291 45 2016-01-05 887 295 45 2015-12-05 887 296 45 2015-11-07 887 301 45 2015-10-06 888 301 45 2015-09-05 887 301 45 2015-08-04 888 301 45 2015-07-03 888 300 45 2015-06-05 888 301 46 2015-05-02 885 298 45 2015-04-04 884 297 44 2015-03-07 886 298 44 2015-02-06 885 303 44 2015-01-07 885 304 45 2014-12-06 886 304 45 2014-11-01 884 302 45 2014-10-04 881 303 46 2014-09-06 878 309 44 2014-06-13 875 307 44 2014-05-02 874 306 44 2014-04-04 876 306 44 2014-03-01 876 306 43 2014-01-11 872 305 42 2013-10-05 854 293 40 2013-08-31 855 295 41 2013-07-20 852 297 40 2013-04-10 838 286 41 2013-03-03 841 289 41 2013-02-02 843 291 41 2012-12-15 845 310 41 2012-03-23 818 310 39 2012-02-01 813 307 40 2011-04-28 768 291 37 2011-02-27 762 288 36 2010-05-02 730 289 34 2010-04-01 727 291 33 2010-03-16 727 293 33 2009-12-16 716 290 33 2009-09-09 700 288 32 2009-03-27 677 287 29 2009-01-10 662 290 30 2008-08-17 635 290 29 2008-03-03 571 247 28 2008-01-02 337 260 28 2007-12-28 336 261 28 2007-09-03 264 258 27 2007-07-24 287 256 27 2007-06-17 280 249 27 references: http://www.balug.org/#Lists

1 0

(forw) linuxmafia.com 2024-06-04 02:02 System Events
by Rick Moen 10 Jun '24

10 Jun '24

More of same, involving back-to-back NOTIFY traffic about mpaoli.net, allegedly originating from master nameserver 96.86.170.226 . Michael, I greatly doubt your nameserver is doing this. mpaoli.net's zonefile is pretty unchanging. I suspect Comcast middleman fsckery. Thoughts? ----- Forwarded message from logcheck system account <logcheck(a)linuxmafia.com> ----- Date: Tue, 04 Jun 2024 02:02:01 -0700 From: logcheck system account <logcheck(a)linuxmafia.com> To: root(a)linuxmafia.com Subject: linuxmafia.com 2024-06-04 02:02 System Events System Events =-=-=-=-=-=-= Jun 4 01:47:15 linuxmafia named[15622]: zone mpaoli.net/IN: Transfer started. Jun 4 01:47:15 linuxmafia named[15622]: transfer of 'mpaoli.net/IN' from 96.86.170.226#53: connected using 96.95.217.99#52012 Jun 4 01:47:15 linuxmafia named[15622]: zone mpaoli.net/IN: transferred serial 1717468800 Jun 4 01:47:15 linuxmafia named[15622]: transfer of 'mpaoli.net/IN' from 96.86.170.226#53: Transfer completed: 1 messages, 6 records, 546 bytes, 0.064 secs (8531 bytes/sec) Jun 4 02:00:09 linuxmafia named[15622]: zone mpaoli.net/IN: Transfer started. Jun 4 02:00:09 linuxmafia named[15622]: transfer of 'mpaoli.net/IN' from 96.86.170.226#53: connected using 96.95.217.99#57758 Jun 4 02:00:09 linuxmafia named[15622]: zone mpaoli.net/IN: transferred serial 1717491608 Jun 4 02:00:09 linuxmafia named[15622]: transfer of 'mpaoli.net/IN' from 96.86.170.226#53: Transfer completed: 1 messages, 15 records, 1266 bytes, 0.072 secs (17583 bytes/sec) ----- End forwarded message -----

3 5

Re: [BALUG-Admin] Comcast Service Ticket CR144883981
by Michael Paoli 07 Jun '24

07 Jun '24

Ah ... sounds good. So ... I'm guessing soon...ish, you'll have 2603:3024:180d:f100:50:242:105:34 (nsx.sunnyside.com.) operational again (no extreme rush) ... or at least nsx.sunnyside.com. regaining an operational AAAA that also works for DNS. I noticed earlier it wasn't working ... then subsequently you apparently dropped the AAAA record for it (perfectly fine thing to do while it's not working!) ... I did try the IP directly - still no DNS response, but I note also that that AAAA record hasn't been restored yet either ... or any AAAA record for that domain. $ eval dig @ns0.sunnysidex.com. +noall +answer +norecurse nsx.sunnyside.com.\ A{,AAA} nsx.sunnyside.com. 600 IN A 50.242.105.52 $ https://dnsviz.net/d/balug.org/Zl6vNw/responses/ https://dnsviz.net/d/balug.org/ZmGAnw/responses/ https://dnsviz.net/d/balug.org/ZmHuow/responses/ > 19 tickets closed almost immediately without comment Let's see, if we have a ticketing system, and highly incentivized folks to close tickets quickly, we get ... lots of tickets closed quickly ... doesn't mean anything gets fixed. And yes, have seen this before ... alas, even in some departments/areas at some employers I've worked at. "Be careful what you measure." (And how one uses it). Same employer, a much more astute manager with a much better functioning department ... how did they do it? They surveyed the customers, and used that as a large measure of determining how well the technicians were doing at getting issues solved ... not how quickly the techs closed tickets. Alas, that highly well performing department stuck out like a sore thumb ... so ... eventually management "fixed" that issue ... by subsuming that department into the other, thus ensuring there wouldn't be such a good standout to embarrass the rest. Anyway, glad your Comcast issue finally got resolved. < From: Michael Paoli <michael.paoli(a)berkeley.edu> < Date: Tue, Jun 4, 2024 at 4:21\xe2\x80\xafPM < Subject: Re: [BALUG-Admin] (forw) linuxmafia.com 2024-06-04 02:02 System Events < To: Rick Moen <rick(a)linuxmafia.com> < Cc: BALUG-Admin <balug-admin(a)lists.balug.org>, Al <aw009(a)sunnyside.com> < < And thirdly - relatively minor issue. Al's got < (at least last I checked, yesterday or so) issues with < 2603:3024:180d:f100:50:242:105:34 (nsx.sunnyside.com.) < not responding. On Thu, Jun 6, 2024 at 7:45 AM Al <aw009(a)sunnyside.com> wrote: > > The manager that took one of my tickets and refused to let it be closed has helped me to finally get my case resolved. > I have tested access from AWS successfully, and the modem does in fact seem to have my /56 back in it instead of what > looked very much like a dynamic /64. > It's also amazing that anyone talked to me at all. I had 19 tickets closed almost immediately without comment. > > > -------- Forwarded Message -------- > Subject: Comcast Service Ticket CR144883981 > Date: Thu, 6 Jun 2024 14:12:18 +0000 > From: > To: awcomcast(a)sunnyside.com <awcomcast(a)sunnyside.com> > > > Good morning, > > > > I am reaching out to you in regards to ticket CR144883981. This was in regards to reclaiming your original IPv6 prefix. I worked with our device support, and we were able to reclaim 2603:3024:180d:f100 for you. As of this morning, the IPv6 has been restored onto your modem. > > > > > > Thank you for using Comcast, > > > > Shana Rich > > Tech 4, CSSA (ABS) > > Complex & Strategic Service Assurance > > Avail Hours Mon-Fri, 8:00am – 4:30pm MST > > Comcast Business Services

2 3

(forw) Re: Comcast Business apparently blocking 5353 UDP Re: linuxmafia.com "retry limit exceeded"
by Rick Moen 07 Jun '24

07 Jun '24

----- Forwarded message from Al <awbalug(a)sunnyside.com> ----- Date: Tue, 4 Jun 2024 16:29:04 -0700 From: Al <awbalug(a)sunnyside.com> To: Rick Moen <rick(a)linuxmafia.com> Subject: Re: [BALUG-Admin] Comcast Business apparently blocking 5353 UDP Re: linuxmafia.com "retry limit exceeded" Rick, you're at the right place - that gear icon and right side panel on business.comcast.com is just the right thing. And I think the situation as you're outlining it is right to me. So the answer to your question, broadly, is yes I think you have it right. If you end up at securityedge.comcast.com, IMHO you've gone too far. My sense is that all that stuff is disabled back at the right side panel... Once SE (security edge) is disabled I think everything is. That said, you're being smart about it - if symptoms persist, drill down and look into individual settings for various elements of SE and just make sure they're all off - in case Comcast can't quite sort out how to actually disable stuff. AFAIK however your nets (yours and Michaels) are unrestricted. My tests from here are that access to both 96.86.170.229 and 96.95.217.99 on port 53 is not blocked (and not just those /32s but the entire subnet in each case). I am looking back over email from the last few days trying to sort out where 73.189.65.18 crept into the conversation. As I mentioned I have been unable to focus sufficiently on this the last few days, and missed where that came from. I also haven't looked closely enough at the discussion to see if what I am trying to reproduce isn't exactly where you're having trouble. I'll go back over the notes and see if I can pay more attention to the details and whether I can actually add any insight to the discussion. Al ----- End forwarded message ----- To clarify, I noticed "73.189.65.18" as the source of NOTIFYs for Michael's domains, which can legitimately come _only_ from Michael's authoritative nameserver, IP 96.86.170.229. And 73.189.65.18 is Comcast's _own_ IP, not Michael's. :r! dig -x 73.189.65.18 +short c-73-189-65-18.hsd1.ca.comcast.net. So, something is rotten, there. I'm immediately inclined to suspect that Comcast is playing man-in-the-middle games with DNS traffic. Which, if true, suggest Comcast acting like a rogue state security agency or one operating on behalf of a totalitarian state. Not a good look.

4 16

DNS: new root hints 2024-05-12 ... 2024-05-28
by Michael Paoli 05 Jun '24

05 Jun '24

FYI, there's new root hints file as of 2024-05-28: https://www.internic.net/domain/named.root see also: https://www.iana.org/domains/root/files Also, Debian stable isn't quite caught up to that yet (though I expect it will likely be with upcoming stable update). And yes, "newer" (/non-ancient) BIND versions are "smart" enough to catch this, notice, and complain (the bit in the logs was what first caught my attention on it). times UTC / GMT0: # cat /etc/debian_version; sed -ne '3,4p;4q' /etc/bind/named.conf.default-zones && dpkg -S /usr/share/dns/root.hints && dpkg -l dns-root-data | grep '^ii '; diff -U0 /usr/share/dns/root.hints <(su - test -c 'curl -s https://www.internic.net/domain/named.root') 12.5 type hint; file "/usr/share/dns/root.hints"; dns-root-data: /usr/share/dns/root.hints ii dns-root-data 2023010101 all DNS root data including root zone and DNSSEC key --- /usr/share/dns/root.hints 2023-01-11 07:22:00.000000000 +0000 +++ /dev/fd/63 2024-06-05 05:57:26.860941086 +0000 @@ -12,2 +12,2 @@ -; last update: January 01, 2023 -; related version of root zone: 2023010101 +; last update: May 28, 2024 +; related version of root zone: 2024052801 @@ -24,2 +24,2 @@ -B.ROOT-SERVERS.NET. 3600000 A 199.9.14.201 -B.ROOT-SERVERS.NET. 3600000 AAAA 2001:500:200::b +B.ROOT-SERVERS.NET. 3600000 A 170.247.170.2 +B.ROOT-SERVERS.NET. 3600000 AAAA 2801:1b8:10::b # May 12 20:45:20 tigger named[3452]: checkhints: b.root-servers.net/A (170.247.170.2) missing from hints May 12 20:45:20 tigger named[3452]: checkhints: b.root-servers.net/A (199.9.14.201) extra record in hints May 12 20:45:20 tigger named[3452]: checkhints: b.root-servers.net/AAAA (2801:1b8:10::b) missing from hints May 12 20:45:20 tigger named[3452]: checkhints: b.root-servers.net/AAAA (2001:500:200::b) extra record in hints

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

BALUG-Admin