can not resolve remote hostname

[stephenph]

Expected behavior

Send logs to remote server

Actual behavior

Cannot resolve hostname : Resource temporarily unavailable

Steps to reproduce the behavior

configure rsyslog.conf to transmit logs to remote server using FQDN:

Environment

• rsyslog version: 8.1907.0 (aka 2019.07)

• platform: x86_64-redhat-linux-gnu (Fedora 29)

• for configuration questions/issues, include rsyslog.conf and included config files

sample forwarding rule

action(type="omfwd"

# An on-disk queue is created for this action. If the remote host is

# down, messages are spooled to disk and sent when it is up again.

queue.filename="fwdRule1" # unique name prefix for spool files
queue.maxdiskspace="1g" # 1gb space limit (use as much as possible)
queue.saveonshutdown="on" # save messages to disk on shutdown
queue.type="LinkedList" # run asynchronously
action.resumeRetryCount="-1" # infinite retries if host is down

# Remote Logging (we use TCP for reliable delivery)

# remote_host is: name/ip, e.g. 192.168.0.1, port optional e.g. 10514

Target="" Port="514" Protocol="tcp")

NOTE: This same configuration is being used on other servers with no error. Port 514 is open on firewall I have also set selinux to permissive. I am able to ping and ssh to rsyslog remote server

[alorbach]

The Target is left empty oj purpose for this issue?
From the error, I would say its a local issue related to a failed dns request.

[hugmuhnuts]

Centos 7
rsyslogd 8.2012.0

Not sure why my Centos host was refusing to resolve one of many hosts being monitored, but installing bind utilities fixed it for me.

$ yum install bind-utils