nanog mailing list archives
Re: route: 0.0.0.0/32 in LEVEL3 IRR
From: Frank Habicht <geier () geier ne tz>
Date: Tue, 30 Jan 2024 22:39:13 +0300
Seems it disappeared now and we can go back to regular programming. Thanks to those who did that. Frank [frank@fisi ~]$ whois -h rr.level3.com 0.0.0.0/32 [Querying rr.level3.com] [rr.level3.com] % No entries found for the selected source(s). [frank@fisi ~]$ On 30/01/2024 19:37, Job Snijders via NANOG wrote:
On Tue, Jan 30, 2024 at 07:28:01PM +0300, Frank Habicht wrote:I believe that the entry of route: 0.0.0.0/32 does not serve any good purpose?I don't think so either, I've created an issue to prevent that in future releases of IRRd v4: https://github.com/irrdnet/irrd/issues/906 Thanks for noticing that! It'll be up to Lumen to remove the record at hand. Kind regards, Job
Current thread:
- route: 0.0.0.0/32 in LEVEL3 IRR Frank Habicht (Jan 30)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Dave Taht (Jan 30)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Rubens Kuhl (Jan 30)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Tom Beecher (Jan 31)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Owen DeLong via NANOG (Jan 31)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Frank Habicht (Jan 31)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Rubens Kuhl (Jan 30)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Dave Taht (Jan 30)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Job Snijders via NANOG (Jan 30)
- Re: route: 0.0.0.0/32 in LEVEL3 IRR Frank Habicht (Jan 30)