2 Apr 2007 15:19
Re: ISSUE: Possibility to use non-resolvable domain name as path-identity
Charles Lindsey <chl <at> clerew.man.ac.uk>
2007-04-02 13:19:09 GMT
2007-04-02 13:19:09 GMT
In <460E807D.14F3 <at> xyzzy.claranet.de> Frank Ellermann <nobody <at> xyzzy.claranet.de> writes: >Charles Lindsey wrote: >> And all I am asking is that it SHOULD resolve. >For which query types (apart from soa and ns) ? A type 99 record >"v=spf1 -all" won't help for the purposes of news (in fact it would >be very near to pointless without a corresponding SMTP server, MTAs >can reject MAIL FROM:<whatever <at> news17.news-servers.example.com> if >there's no IP and no MX, without wasting time for SPF checks). Even NS would be interesting, if there is nothing else. >SRV or similar records could be interesting, if the "news-servers" >at example.com wish to enumerate their hosts news17, etc. That's >only a future possibility mentioned in the "URI" I-D so far, and >it's unrelated to any "SHOULD resolve (some query types TBD)". >> Then if it doesn't, it immediately draws attention to itself as a >> cause for suspicion. >I don't recall a single case where I tried `nslookup -q=any` for a >path identity, and I looked into the peering database a few times >while trying to figure out path header fields. Admittedly I'm more >interested in mail abuse today. Actually, I quite often use ANY (with 'dig' rather than 'nslookuop') when I am not quite sure what I am looking for.(Continue reading)
RSS Feed