Re: DNS caching(?) page-hangup issues and Opera 10.X

Kenneth Crudup <[email protected]> writes:

> On Thu, 22 Jul 2010, Eirik Byrkjeflot Anonsen wrote:
>
>> In the good news department, we believe we have found the problem with
>> name lookups when the network changes.  It seems glibc does not notice
>> changes to the DNS server addresses automatically.  But it seems it does
>> provide a function that can force it to reload the configuration.  There
>> is currently some discussion on how we can use it without breaking
>> anything.
>
> You mean res_init()?

Yes.

> What about a hidden button or something?! Maybe if you're sent a signal?

We'll probably primarily go for calling it when a name lookup fails and
then retry the lookup.  We might want to add some other cases as well
(e.g. when known configuration files are changed or when we detect a
change in the network infrastructure otherwise).

I don't think our main problem is to detect when to call the function.
Not yet, anyway.  I think the main problem right now is calling it
correctly when we want to call it.  The host resolution code is less
than pretty, as it has to deal with multiple subtly incompatible
resolver libraries...

eirik
--
Opera-Linux: https://list.opera.com/mailman/listinfo/opera-linux
More lists: https://list.opera.com/mailman/listinfo/
Unsubscribe: mailto:[email protected]?subject=unsubscribe