Forum Discussion

Cirrus

May 12, 2015

FQDN Node "flush"

Hi all, we are deploying new Virtual Servers in 11.6.0 using the FQDN node feature.. we have observed that when the DNS record for the FQDN is changed that the old record remains as an ephemer...

Employee

May 12, 2015

I am wondering if this can be flushed when a new record is learned after the timeout period. ?

can you try to restart bigd? i may be wrong but i think bigip will resolve fqdn node when bigd is restarted.

 restart bigd

[root@ve11c:Active:In Sync] config  tmsh list ltm node google
ltm node google {
    fqdn {
        autopopulate enabled
        name www.google.com
    }
    state fqdn-up
}
[root@ve11c:Active:In Sync] config  date; tmsh restart sys service bigd
Tue May 12 19:25:42 SGT 2015
[root@ve11c:Active:In Sync] config 

 tcpdump

[root@ve11c:Active:In Sync] config  tcpdump -nni 0.0 -s0 port 53
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on 0.0, link-type EN10MB (Ethernet), capture size 65535 bytes
19:26:01.144898 IP 172.28.24.13.33478 > 8.8.8.8.53:  26437+ A? www.google.com. (32) out slot1/tmm1 lis=
19:26:01.150778 IP 8.8.8.8.53 > 172.28.24.13.33478:  26437 6/0/0 A 74.125.130.105, A 74.125.130.103, A 74.125.130.147, A 74.125.130.99, A 74.125.130.106, A 74.125.130.104 (128) in slot1/tmm1 lis=
19:26:06.149613 IP 172.28.24.13.48936 > 8.8.8.8.53:  26437+ A? www.google.com. (32) out slot1/tmm1 lis=
19:26:06.157343 IP 8.8.8.8.53 > 172.28.24.13.48936:  26437 5/0/0 A 173.194.117.115, A 173.194.117.114, A 173.194.117.113, A 173.194.117.116, A 173.194.117.112 (112) in slot1/tmm1 lis=