IP Tunneling - Reverse DNS lookup fails

[joman]

We have recently started using Networker 7.1.2 clients.
Since then, we see diagnostics like these:
*frigg:/opt save: Diagnostic: Reverse DNS lookup failed for address 10.255.227.253
With the old clients (5.1.1) against the same backup server (7.1.1), we see no such messages.
After some fooling around, we found out that the messages appear on clients where we use IP tunneling (the application is Alcatel 5620 NMS, which uses tunneling).
The address 10.255.227.253 is really a tunneling alias for the client itself, and we get one diagnostic for each tunnel defined on the client (up to some 25).
For the client "frigg" we get two diagnostics, and it has two tunnels:
frigg# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 193.162.144.176 netmask ffffff00 broadcast 193.162.144.255
ether 8:0:20:fc:c6:46
tdd3: flags=10088f1<UP,POINTOPOINT,NOTRAILERS,RUNNING,NOARP,MULTICAST,PRIVATE,IPv4> mtu 1480 index 30
inet 10.255.227.253 --> 10.255.235.253 netmask ff000000
ether 19:31:62:14:41:67
tdd4: flags=100a8f1<UP,POINTOPOINT,NOTRAILERS,RUNNING,NOARP,MULTICAST,UNNUMBERED,PRIVATE,IPv4> mtu 1480 index 31
inet 10.255.227.253 --> 10.255.231.253 netmask ff000000
ether 19:31:62:14:41:66

It seems the backups are quite OK.
But, anyway, can we get rid of them?

/John M

 

[wallace88]

try adding those i.p. addresses in the the client's alias list.

 

[joman]

Thanks, wallace88
Sorry about the delay.

As I understand you, this is what I should do:
add something like
10.255.227.253 frigg_tunnel
in /etc/hosts, and then add 'frigg_tunnel' to the aliases
for frigg?

It will take more than a week before I'll be able to try.

/John M

 

[wallace88]

that's about right...


Try just putting 10.255.227.253 into alias field directly.