[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: TCP Wrapper Question



I didn't mention that the client machines run on a windows [Active Directory] DNS/DHCP servers. The windows nameserver is 172.16.164.100, which is referenced in /etc/resolv.conf 

>DNS and DHCP on the same box, so that (possibly?) DHCP can update 
>DNS with device names?  Otherwise, how do you map name to IP?

Thing is when the machines names change, the servers can still look them up with proper details. [My laptop is on DHCP and generally gets a new IP every 48hrs, and I can still look this machine up both ways].

Thing is im not sure *where* my problem is. The machine can obviously connect to the DNS server and get the details, so why isn't tcpd doing it?

Thanks

B

-----Original Message-----
From: Ron Johnson [mailto:ron.l.johnson@cox.net] 
Sent: Tuesday, March 16, 2010 1:52 PM
To: debian-user@lists.debian.org
Subject: Re: TCP Wrapper Question

On 2010-03-16 08:14, Brian O'Mahony wrote:
[snip]
> 
> However things are being logged to log files, using IPs, and not machine 
> names.
> 
> Both auth and syslog have IP entries which are pretty useless to me with 
> things being on a DHCP network [which I also have no control over].
> 

DNS and DHCP on the same box, so that (possibly?) DHCP can update 
DNS with device names?  Otherwise, how do you map name to IP?

Another way would be to have the DHCP server to log MAC-IP-timestamp 
tuples, load it into some tool (whether it be a DBMS, spreadsheet or 
Python/Perl/etc list) and use that to derive what you need to know.

-- 
Obsession with "preserving cultural heritage" is a racist impediment
to moral, physical and intellectual progress.


-- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] 4B9F8D19.7050309@cox.net">http://lists.debian.org/[🔎] 4B9F8D19.7050309@cox.net



The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank you.


Reply to: