All geek questions in one place

Should I do a WHOIS search with TcpClient.Connect () in C #?

The client asked us to do a dynamic whois search on the main page of our ASP.NET site based on the IP address of the user accessing the site.

The implementation will be approximately as described here:

http://www.aspheute.com/english/20000825.asp

However, I noticed that this code connects to whois.networksolutions.com. I think this may not scale very well if we initiate a connection to this remote server each time the page loads.

For example, let's say that 1000 different users got to the home page - this will lead to the initiation of many connections.

Any thoughts on this?

+3
source share
3 answers

Yes, it can take a long time. The amount of "high cost" really depends on the network connection between your server and the remote server and the response time of the remote server. You might consider caching the response if your requests are not different from each other (which is unlikely to be the case for a whois domain request entered by end users). The big problem is that the remote server can block you if it sees too many connections from the same IP address.

+3
source

, DNS... , DNS- -. DNS, DNS- ISP.

whois DNS, , , .

, ... , - , , , ?

+1

, , , .

0

Source: https://habr.com/ru/post/1734141/

More articles:


All Articles