Forum Discussion
NimbostratusV11.3 GTM queries going to BIND
Need some help with something that I am not able to explain. I have a V11.3 GTM that has its pool set for Global Availability as Preferred and round-robin as alternate and fallback is set to return-to-dns. What I am experiencing is that, even though Preferred is available and working, some requests are going to Bind, the issue with this is that its returning DR IPs that are not live.
Here is the stats and the Returned to DNS count keeps growing. I reset the stats and watched just to make sure it wasn't a point in time issue that we did not know but its happening regularly. This date is for the past hour.
Status
Availability : available
State : enabled
Reason : Available
Load Balancing
Preferred 230
Alternate 0
Fallback 0
Returned from DNS 0
Returned to DNS 110
Miscellaneous
Connections Dropped 0
Local DNS Persisted 0
Here is my pool config:
gtm pool XXXXXXXXX_prod {
alternate-mode round-robin
app-service none
canonical-name none
description none
dynamic-ratio disabled
enabled
fallback-ipv4 any
fallback-ipv6 any6
fallback-mode return-to-dns
limit-max-bps 0
limit-max-bps-status disabled
limit-max-connections 0
limit-max-connections-status disabled
limit-max-pps 0
limit-max-pps-status disabled
load-balancing-mode global-availability
manual-resume disabled
max-address-returned 1
members {
abcltmv03-04:xxxxxxx_prod_443_abc {
app-service none
depends-on none
description none
enabled
limit-max-bps 0
limit-max-bps-status disabled
limit-max-connections 0
limit-max-connections-status disabled
limit-max-pps 0
limit-max-pps-status disabled
monitor default
order 1
ratio 1
}
xyzltmv03-04:xxxxxxx_prod_443_xyz {
app-service none
depends-on none
description none
enabled
limit-max-bps 0
limit-max-bps-status disabled
limit-max-connections 0
limit-max-connections-status disabled
limit-max-pps 0
limit-max-pps-status disabled
monitor default
order 0
ratio 1
}
}
metadata none
monitor default
partition Common
qos-hit-ratio 5
qos-hops 0
qos-kilobytes-second 3
qos-lcs 30
qos-packet-rate 1
qos-rtt 50
qos-topology 0
qos-vs-capacity 0
qos-vs-score 0
ttl 30
verify-member-availability enabled
}
Appreciate your help.
1 Reply
wowchensI figured this, I forgot to enable ipv6-no-error-response and all AAAA queries are being sent to Bind, which is expected behavior. Not sure where the queries are coming from but this setting takes care of it. It would be nice if I can track where these requests are coming from, may be use a specific tcpdump filter for IPV6 queries?
