Piotr Da³ek wrote:
>
> Seems like dnsstuff.com may have more nameservers or their own database.
> Since it doesn't work with simple "ping -a" too, I wouldn't worry about
> this.
>
The problem is that TWSocket.ReverseDnsLookup returns error "No Data".
TDnsQuery fails also. HLembke\TDnsQuery retur
Hello!
>> PD> Seems like dnsstuff.com may have more nameservers or their own
>> database.
>PD> Since it doesn't work with simple "ping -a" too, I wouldn't worry about
>PD> this.
> I only see thoses two IPs from dnsstuff.com, which field/option did you
> use ?
To be honest, I didn't used dnsstuf
Hello Piotr,
I only see thoses two IPs from dnsstuff.com, which field/option did you
use ?
Regards.
PD> Hello!
>> www.microsoft.de resolves to
>> 207.46.130.108 and 207.46.250.119
>> WSocket.ReverseDnsLookup(207.46.130.108/207.46.250.119)
>> as well as NSLookup fails, tested with multiple nam
Hello!
> www.microsoft.de resolves to
> 207.46.130.108 and 207.46.250.119
> WSocket.ReverseDnsLookup(207.46.130.108/207.46.250.119)
> as well as NSLookup fails, tested with multiple name servers.
> Does somebody know why?
> But http://www.dnsstuff.com/ returns 15 records.
C:\WINDOWS\Profiles\
Hi,
www.microsoft.de resolves to
207.46.130.108 and 207.46.250.119
WSocket.ReverseDnsLookup(207.46.130.108/207.46.250.119)
as well as NSLookup fails, tested with multiple name servers.
Does somebody know why?
But http://www.dnsstuff.com/ returns 15 records.
---
Arno Garrels [TeamICS]
http:/
