March 2025 - NANOG - lists.nanog.org

[NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures
by Volkan SALiH 03 Mar '25

03 Mar '25

he owns content-heavy (mostly outbound) network , as6939 is not eyeball. so he has to do peering for their own good... they gained tier 1.5 position thanks to their peering links. they are not in position to change peering policy to selective or restrictive until they convince cogentCO to peer them feeless (hopefully never! thanks to god!) think big, think wide-open. dont be a fanatic of freeloaders of IXPs/ISPs... most datacenters peer for free, as they are/would be happy with ratios. sincerely.

1 0

DNS and subdomains
by Harry Hoffman 03 Mar '25

03 Mar '25

Hi Folks, Feel free to tell me this isn't the proper place for my question but given that networking and DNS are hand in hand I thought it might be reasonable to ask here. In working with several OSINT sources for domain processing it seems like the way domains and subdomains are processed essentially equates subdomains with FQDNs. For example, several APIs (and even ChatGPT) classify the following: access.api.bbc.com account-api.api.bbc.com account-api.int.api.bbc.com account-api.stage.api.bbc.com account-api.test.api.bbc.com account-cdn.test.api.bbc.com with subdomains as either: all subdomains as api.bbc.com or as subdomains of access.api, account-api.api, account-api.int.api, etc. instead of classifying as: api.bbc.com int.api.bbc.com stage.api.bbc.com test.api.bbc.com Has this become common practice? Is there a definitive way to determine subdomains? I seem to recall that "older" dns server software wouldn't allow this but it could be that my memory is faulty. Thanks! Cheers, Harry

11 18

[NANOG] Re: DKIM and list policies
by Bryan Fields 03 Mar '25

03 Mar '25

On 3/3/25 04:38, Niels Bakker via NANOG wrote: > Agreed on both counts. Look at this monstrosity: > > Subject: [NANOG] Re: [NANOG]Re: Hardware for MPLS/SR network That happened since the "[NANOG]" was changed to "[NANOG] " and mailman will only catch the current prefix. Mailman will find any instance of "[NANOG] " in the header, remove it and a "Re: " if at the start of the subject. Currently the list is configured to rewrite the from as being from the list, ex: "From: Bryan Fields via NANOG <nanog(a)lists.nanog.org>". It is possible to see if the signature on the inbound message was valid by looking at the "Authentication-Results: lists.nanog.org" header, as DKIM-Filter is running on the mailserver. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

3 2

[NANOG]testing 25
by Bryan Fields 01 Mar '25

01 Mar '25

-- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 0

[NANOG]testing fix
by Bryan Fields 01 Mar '25

01 Mar '25

-- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

2 6

[NANOG]Testing456
by Valerie Wittkop 01 Mar '25

01 Mar '25

*Valerie Wittkop* Program Directorvwittkop(a)nanog.org | +1 734-730-0225 <+17347300225> (mobile) | www.nanog.org NANOG | 305 E. Eisenhower Pkwy, Suite 100 | Ann Arbor, MI 48108, USA ASN 19230

3 2

[NANOG]Testing nanog@lists.nanog.org
by Greg Newman 01 Mar '25

01 Mar '25

Testing

1 0

[NANOG]testing123
by Bryan Fields 01 Mar '25

01 Mar '25

-- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 0