Thread: gethostbyaddr is slow

gethostbyaddr is very slow in returning when the host can't be found. (i.e. when it returns NULL)

Is there anyway to speed this up? Is getnameinfo any quicker in this respect?

Thanks.

Well doesn't it need to check with a DNS server (check what happens when you run ethereal).
Since not finding something is bound to take the longest (maybe there are timeouts).

For instance, the traceroute command resolves IP addresses if you don't specify the -d option.

If it had to wait for gethostbyaddr to return for addresses which didn't have a hostname, the program would be very slow.


It doesn't however and flicks through the nodes without a hostname just as fast as the ones which do.

Would this because they set some kind of timeout facility?
What would be the most efficient way of doing this?

Thanks.

Originally Posted by eth0

For instance, the traceroute command resolves IP addresses if you don't specify the -d option.

If it had to wait for gethostbyaddr to return for addresses which didn't have a hostname, the program would be very slow.


It doesn't however and flicks through the nodes without a hostname just as fast as the ones which do.

I don't think you understand what you're saying... nor how trace route works.

you see, the network works with ip, not hostnames!
the idea of hostnames was created because they are easier to remember than ip addresses.

now a trace route all it does is display the routers on the route to the target, by incrementing the TTL feild of the icmp packet (you should google it)

what i am trying to say, trace route does not work with hostnames, but resolves the ip to hostname for YOU...
the -d option tells the tracert program to simply do it's job without the extra "bulls.hit" , like resoloving ip to hostname, which obvisuly takes time.
you should also lookup how dns is resolved, this will explain to you why does it take sometime so long for a dns name / ip to be resolved.

plus, i'm agains resetting the timeout value of the dns lookup.
because you might timeout while the answer is on it's way to you.

Originally Posted by Devil Panther

I don't think you understand what you're saying... nor how trace route works.

I know 100% how traceroutes work, I'm a CCNP network engineer.

As traceroute works with IP addresses, in order for me to display the hostname, I need to do a reverse lookup.
My reason for asking this question was, if the IP address in question doesn't have a hostname, it takes gethostbyaddr around 10 seconds to return. This is unacceptable for my program as it brings it to a virtual standstill.


anonytmouse, thanks for your response, the netbios lookup would make sense. I will use getnameinfo instead. I'll reply in this thread as to the results.

Originally Posted by eth0

I'll reply in this thread as to the results.

getnameinfo returns immedietley, and a packet capture shows identical behaviour in both the MS tracert and my rewrite.

Thanks.

Originally Posted by eth0

I know 100% how traceroutes work, I'm a CCNP network engineer.

You may understand the protocol implementation (how it uses ICMP or UDP), but that doesn't tell you JACK about how it was programed.

The point he was making, is if you tell the traceroute not to look up the domain name, it simple skips that, where as if you request the domain name to be looked up, it will request that info via DNS, and may take a while, causing a lockup or stutter effect.
One way you might be able to deal with this, is some how break the lookup into a seperate thread, and simply use the IP untill the name is either found, or deemed unknkown, that way it doesn't interupt with the normal flow, and cause a stuttering or lockup effect (so to speak). Their are probably other ways to do it as well.