|>
|> Netscape seems to have problems with the local nameserver... Even if I try
|> to access a local html page, the browser still hangs right away. It's not
|> agreeing with the dns server, for some reason. Has anyone experienced
|> this?
|>
|
|No not netscape have the problem but if you set up an name server you have to
|
|ensure that all request that come to him are able to be answerd or rejected.
|
|I think you tell him he is authoritiv for "." or you gave him an ip for toher
|name
|server he canīt reach. So he accept the query but canīt resolv it.
|
|A trick to solve it is log all request and make the adress local for him ex.
|Netscape ask "home.netscape.com" add
|"home.netscape.com.my.domain.de = 127.0.0.1"
|so he replay and netscape is happy.
I've found that netscape doesn't try to connect to a netscape-site but
tried to resolve news-server instead. For instance, I had files
$HOME/.newsrc-<not-a-valid-host> and it tried to resolve
<not-a-valid-host>. You may check your situation by sending a 'kill -WINCH
<named-pid>' to your locally running named. This will log all requests to
syslog.
M.
-- Michael Eyrich, PRZ, TU-Berlin michey@prz.tu-berlin.de- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu