[plug] Strange dns/ip issue

[Carl Gherardi]

Hey Julian,

On 5/17/05, Julian Clark <clarkjj at gmail.com> wrote:
> If I ping a name for resolution, or an ip address, I can then access
> that address using normal http means. Unfortunately the first ping
> takes a very long time, and it seems that normal http times out in the
> time for this to resolve.

> I'm using dhcp at home, though I'm not sure if the appropriate config
> files are happy or not (I'm guessing not)
> resolv.conf has single entry pointing to router's ip address.
> 
> Using DHCP on a friends network also, I experienced the same issue.
> 
> Any suggestions?

This isn't linux specific, but triggers mroe often under linux.

Dont use the routers dns caching/redirection. I've found this to be
problematic in all setups i've used previously. I think the problem
stems from being unable to resolve the domain name of the router
itself (something to do with preventing dns poisoning?? anyone? )ie.
Client looks up routers ip for domain name (which the router often
passes to the real dns server), gets nothing then does the lookup
anyway. The timeout happens 'cos the first one takes a bit, and is
then cached.

If you are using dhcp - set up the router to distribute the adsl
providers dns servers to any clients and your problems should
disappear.

HTH

Carl G