Problem with wrong hostnames in tcpdump

[Barry Margolin]

In article <317A6631B185D3119C8A005004549D7DF2F7 at AMANDA>,
Patrick Ludolph <pludolph at offix.de> wrote:
>I have a problem with wrong hostnames e.g. when I do a tcpdump.
>The log shows that a connection was established to a host in a virtual
>domain. If I add a new zone in bind, tcpdump resolves every connection to
>the new domain. The same problem with ntop. How can I change it to show me
>the real hostname of the machine?
>
>I'm using bind 8.1.2 on Linux
>
>Actually I'm not sure if it's really a DNS-problem, but maybe somebody has a
>hint.

This comes from the reverse domain.  It sounds like every time you add a
new forward domain, you're changing the PTR record for your address to
point to that new hostname.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.