SOLVED Travelinman 3 not resolving FQDNs

[jeff.h]

Installed Travelinman 3 per Ward's tutorial and I can't get it to resolve FQDNs. I've tried this on a couple different machines and I get the same result.

It worked Friday night when I did it on one machine, but now it is not working on any others that I try.

When I run ./add-fqdn NAME name.ip.com (sanitized) then select any combination of the service options I get...

The following iptables rules now are in effect for name.ip.com: .
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.

If I cat /root/NAME.iptables I just get ip.name.com and no IP address.

If I ping the FQDN from the CLI it resolves and pings just fine.

I edited ipchecker with account[0]=NAME.iptables and when I run it I get...

./ipchecker: line 33: dig: command not found
Ooops. We gotta a DIG fail problem. Forcing a match on IP to avoid disaster.
Account NAME.iptables OK

 

[wardmundy]

Is this a Raspberry Pi?? Looks like dig is not installed. Have you read this thread?

 

[jeff.h]

This is for a standard 2.0.6.5 PIAF-Green install on a Foxconn box without Incredible PBX that I setup last night. It's working on another one from a 2.0.6.4 PIAF-Green install. Haven't run update-source or any of that on either and they have all modules from base, extended and unsupported installed as well as System Admin and all are fully updated.

EDIT: Ok nevermind... brain fart.... Just installed bind-utils... all is good. Sorry for the confusion.