Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 27 |
Nodes: | 6 (0 / 6) |
Uptime: | 40:37:20 |
Calls: | 631 |
Calls today: | 2 |
Files: | 1,187 |
D/L today: |
24 files (29,813K bytes) |
Messages: | 174,719 |
Mar 31 02:01:39 newsfeed nnrpd[3339866]: ? reverse lookup for 2001:41d0:a:280::1 failed: reverse lookup validation failed -- using IP address for access
Interestingly, news.nntp4.net does not resolve back to that IP, it uses 2001:41d0:700:1273::
Nigel Reed wrote:I'm pretty sure I said in the original message that my IP resolves
Mar 31 02:01:39 newsfeed nnrpd[3339866]: ? reverse lookup for 2001:41d0:a:280::1 failed: reverse lookup validation failed --
using IP address for access
Interestingly, news.nntp4.net does not resolve back to that IP, it
uses 2001:41d0:700:1273::
That's probably why the "reverse lookup validation failed"
otherwise someone could map their IP to any name they like
to get around hostname based access control.
MTAs have done that kind of check "for ages".
BTW: does the DNS resolver used by nnrpd give the expected
result for your own IP?
Mar 31 02:01:39 newsfeed nnrpd[3339866]: ? reverse lookup for 2001:41d0:a:280::1 failed: reverse lookup validation failed -- using
IP address for access
Mar 31 02:01:39 newsfeed nnrpd[3339866]: ? reverse
lookup for 2602:fe64:8::7 failed: reverse lookup validation failed --
using IP address for access
I'm pretty sure I said in the original message that my IP resolves
correctly. You seem to have ignored that paragraph.
All my IPs resolve correctly.
nnrpd claims there is a mismatch between PTR and AAAA -I assume it uses the libc functions.
so what's different in nnrpd vs CLI?
nnrpd claims there is a mismatch between PTR and AAAA -
so what's different in nnrpd vs CLI?
I assume it uses the libc functions.
A view to /etc/nsswitch.conf might be interesting here.