incorrect behaviour of netdb.ResolveHostByAddr
Original Reporter info from Mantis: kelner
-
Reporter name: Alexander Kelner
Original Reporter info from Mantis: kelner
- Reporter name: Alexander Kelner
Description:
netdb.ResolveHostByAddr returns wrong result for reverse DNS lookups, when DNS respond is legal but curly.
Steps to reproduce:
nslookup 8.8.8.8
8.8.8.8.in-addr.arpa name = google-public-dns-a.google.com.
nslookup 188.93.111.66
66.111.93.188.in-addr.arpa canonical name = 66.64/26.111.93.188.in-addr.ar.
66.64/26.111.93.188.in-addr.arpa name = RbNet.kstu-kai.ru.
./test
8.8.8.8 [google-public-dns-a.google.com]
188.93.111.66 [NODOMAIN]
=========================================
program test;
uses netdb,sockets;
function host_by_ip(ip_str: string): string;
var
phe: THostEntry;
domain: string;
begin
if netdb.ResolveHostByAddr(in_addr(StrToHostAddr(ip_str)),phe)
then domain:=phe.name
else domain:='NODOMAIN';
host_by_ip:=domain;
end;
var ip: string;
begin
ip:='8.8.8.8';
writeln(ip,' [',host_by_ip(ip),']');
ip:='188.93.111.66';
writeln(ip,' [',host_by_ip(ip),']');
end.
Mantis conversion info:
- Mantis ID: 34480
- OS: Linux
- Platform: X64
- Fixed in version: 3.3.1
- Fixed in revision: 42934 (#560c0b22)
- Monitored by: » kelner (Alexander Kelner)
- Target version: 3.2.0