We have also noticed this, sometimes when doing a sh ses the users ip
address shows, other times its their number. Currently we are only using
static addresses.
Sometimes netscape etc gives us problems when a user tries to go somewhere,
a DNS error comes up, but after a few minutes of waiting, and a reload it
goes away.
Any ideas anyone?
Cheers
Nathan
>We have had the exact same problems on both our customers DNS and doing sh
>sess's. I have
>noticed that doing a 2nd sh sess usually performs the correct reverse
>lookup and not showing
>the IP. We have both statically and dynamically addressed customers, and
>the problems is
>evident in both cases. Fortunately, a 'reload' in netscape or second
>attempt usually is
>sucessful.
>
>For the record, we have one primary and two secondary servers. The three
>portmasters default
>to the primary and only use one of the secondary servers. DNS is heavily
>used on our system
>but our servers appear to be doing an adequate job of load balancing. And
>no other programs,
>or equipment seems to be experiencing the same problem.
-- Nathan Mercer Technical Director NetAccess Internet Services Christchurch, New Zealand http://www.mac.co.nz/net.htmVoice +64 25 352339 Fax +64 3 3799490 nathan@netaccess.co.nz http://www.newzeal.com
"Venimus, Vidimus, Dolavimus" (we came, we saw, we hacked)
"It is not a bomb; it is a device which is exploding." -Jacques Le Blanc, French ambassador to New Zealand