Forum Discussion
NimbostratusIPv6 DNS queries not matching region
Hello,
I have configured an IPv6 Topology record and pointed it to a region but when i look in the logs they are blank.
record = IP Subnet is 2xxx:xxx:100e:4::/64 State is United States/Illinois weight = 50
logging Rule when DNS_REQUEST { log local2. "IP [IP::client_addr] is in \ continent [whereis [IP::client_addr] continent] \ and country [whereis [IP::client_addr] country] \ and state [whereis [IP::client_addr] state]" }
I see iPv4 being logged correctly but not IPv6, am I missing something?
7 Replies
Cory_50405Noctilucent
For queries arriving at your GTM over IPv6, does anything at all get logged, or is the log entry just not containing the information you expect?
Fab_46677thanks for getting back to me Cory,
Below is a log entry for iPv6 and one for v4
Fab-geotest: IP 2xxx:xxx:xxxe:4:xx:xx:xx:xxx is in continent NA and country US and state
Fab-geotest: IP xx.xx.xxx.69 is in continent NA and country US and state Pennsylvania
The "state" is blank for IPv6 and i am thinking this is why the client is complaining about bouncing between our data centers as the primary algorithm is failing and dropping to secondary, which is round-robin.
- Cory_50405
Yep. If the geolocation database is missing or has stale information, that could certainly be a cause for topology not behaving as expected.
Have you updated your geo DB recently?
http://support.f5.com/kb/en-us/solutions/public/11000/100/sol11176.html
- Fab_46677
I have not. Below is the output, would you say 20131003 is out-of-date?
size of geoip database = 198381578, version = GEO-148 20131003 Build 1 Copyright (c) F5 Networks Inc All Rights Reserved
- Cory_50405
Yes, there is a geolocation DB update from last week on 2 May.
- Fab_46677
ok, thanks.
So manually adding records to the DB do not over ride the updates received from F5? Sorry i am not very familiar with the process.
- Cory_50405
I've never tried to manually add records to the geo DB, only updated it with the latest that F5 releases.
