Logging hostname not getting updated after DNS change

[Akhtar Samo]

Hi,

We have the backup logging server(10.10.10.10) at DR site, and logging server(192.168.100.100) at Production site.

Router(Config)#lip name-server 192.168.1.100

Router(Config)#logging logs.xyz.com

Router# show run | i logging

logging 192.168.100.100

Now whenever we make a record change on the DNS server for 'logs.xyz.com' to 10.10.10.10, that is not getting updated in the router, is there any way the router dynamically resolves logs.xyz.com or refers the router local cache ?

Since the router dns cache(show ip hosts) is timing out after sometime but the router is not updating the logging command ....

Would appreciate your thoughts on it.

Regards,

Akhtar

[Michel Hegeraat]

clear arp?

Cheers,

Michel

[Akhtar Samo]

This has nothing to do with arp. It is a problem related to FQDN resolution on the router.

[Michel Hegeraat]

Given the fact that the running config already has the IP address it seems there is nothing dynamic after that.

If the show startup config still has the FQDN in the logging statement then a reload or perhaps a copy startup  running could give the desired result.

Cheers,

Michel

[Akhtar Samo]

Hi Michel,

The startup config is also having the resolved IP address and I think that this will not get updated automatically after the DNS entry is changed.

One of our customer is actually arguing with us over this behaviour, which has been observed on all platforms (6500, 4500, 2800 and 3800).

We have suggested some manual script based workarounds but they aren't acceptable to the customer.