resolver problem with Opera
Karel J. Bosschaart
karelj at kayjay.xs4all.nl
Sat May 22 11:05:47 PDT 2004
On Sat, May 22, 2004 at 09:24:53AM -0600, Robin Schoonover wrote:
> On Sat, 22 May 2004 13:15:20 +0200, Karel J. Bosschaart wrote:
> >
> > It seems that Opera on -current ignores /etc/hosts on my system: the
> > hostname I type in the address bar is resolved using the nameserver
> > while there is an entry for it in /etc/hosts. Using konqueror, name
> > resolution is as expected, it resolves to the local address specified
> > in /etc/hosts.
> >
>
> I'm not entirely sure, but I think opera loads /etc/hosts into memory at
> start, and never reads it again. Sometimes it seems to check the
> nameserver first, and -then- /etc/hosts, but usually it seems to check
> /etc/hosts first. I'm really unsure on what opera's logic concerning it
> is, and it seems like opera is doing all the dirty work on its own.
The strange thing is that the same Opera version on -stable *does*
check the /etc/hosts first. If I remove /etc/resolv.conf on the -current
machine Opera checks /etc/hosts and resolves the name correctly but
that's obviously not a good solution.
I posted my problem on the Opera/FreeBSD forum hoping someone can clear
this up.
Thanks for the reply,
Karel.
More information about the freebsd-current
mailing list