Re: more spaces in PTRs, this time totisp.net

2021-10-22 Thread Steven Champeon
on Fri, Oct 22, 2021 at 04:05:44AM +, Steven Champeon wrote: > > Anyone? FWIW, I took a look at my scans data and there's a lot of this around. Of the 5477 PTRs with spaces, in approximately ~490 domains*, those with more than twenty hosts with PTRs containing spaces are the following:

Re: more spaces in PTRs, this time totisp.net

2021-10-22 Thread Mark Andrews
\032 is space. Go read STD13 aka RFC 1034 and RFC 1035. -- Mark Andrews > On 22 Oct 2021, at 16:40, Owen DeLong via NANOG wrote: > > \032 is not a space. > > Decimal 32 (0x20, \040) is a space. > \032 is a Ctrl-Z (26 decimal, 0x1a) > > Owen > > >> On Oct 21, 2021, at 22:14 , Mel Beckman

Re: more spaces in PTRs, this time totisp.net

2021-10-22 Thread Ray Bellis
On 22/10/2021 06:39, Owen DeLong via NANOG wrote: > \032 is not a space. > > Decimal 32 (0x20, \040) is a space. > \032 is a Ctrl-Z (26 decimal, 0x1a) In DNS zone files (and dig's presentation format) backslashed numbers are in decimal, not octal - RFC 1035, §5.1. Ray

Re: more spaces in PTRs, this time totisp.net

2021-10-22 Thread t...@pelican.org
On Friday, 22 October, 2021 06:39, "Owen DeLong via NANOG" said: > \032 is not a space. > > Decimal 32 (0x20, \040) is a space. > \032 is a Ctrl-Z (26 decimal, 0x1a) So, someone trying to "undo" in a GUI editor, or a failed attempt to exit 'vi'? Cheers, Tim.

Re: more spaces in PTRs, this time totisp.net

2021-10-21 Thread Mel Beckman
Owen, Ah, so a cross-base typo! :) -mel via cell > On Oct 21, 2021, at 10:40 PM, Owen DeLong wrote: > > \032 is not a space. > > Decimal 32 (0x20, \040) is a space. > \032 is a Ctrl-Z (26 decimal, 0x1a) > > Owen > > >> On Oct 21, 2021, at 22:14 , Mel Beckman wrote: >> >> Typo I’d say.

Re: more spaces in PTRs, this time totisp.net

2021-10-21 Thread Owen DeLong via NANOG
\032 is not a space. Decimal 32 (0x20, \040) is a space. \032 is a Ctrl-Z (26 decimal, 0x1a) Owen > On Oct 21, 2021, at 22:14 , Mel Beckman wrote: > > Typo I’d say. DB-drive DNS servers, which don’t keep their entries in > traditional PTR-record text format, can fall victim to this. Rather

Re: more spaces in PTRs, this time totisp.net

2021-10-21 Thread Mel Beckman
Typo I’d say. DB-drive DNS servers, which don’t keep their entries in traditional PTR-record text format, can fall victim to this. Rather than parse the text every times, they just spit out whatever is in the table column, even if it has embedded spaces. I’ve seen this happen in SnitchDNS. -m