Itismike said:

I learned that nmblookup -A <IP_address> is supposed to return a hostname, and 
it does not. 
----

Ryan Blake said:
Mike,

Have you checked your reverse DNS PTR records? In other words, did you do
an nslookup on 192.168.1.117 to ensure it points back to the host? If
that's not correct, try correcting it and see what happens. For some
reason, I remember having a similar problem and it ended up being a reverse
DNS problem.

~Ryan 
----
No, it doesn't point back to the host:

$ nslookup 192.168.1.117
Server:         192.168.1.1
Address:        192.168.1.1#53
** server can't find 117.1.168.192.in-addr.arpa.: NXDOMAIN

I don't know enough about DNSMasq to know where it keeps reverse DNS PTR 
records. Sounds like more studying for me. :-/

+----------------------------------------------------------------------
|This was sent by [email protected] via Backup Central.
|Forward SPAM to [email protected].
+----------------------------------------------------------------------



------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
BackupPC-users mailing list
[email protected]
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Reply via email to