nsupdate to modify zone in specific views.
we have zone name example.com and we have 2 view (external and internal) so in /var/namedb/ we have zone file db.external.example.com and db.internal.example.com . How can we use nsupdate to modify zone in specific views? because we can't seem to specify view in nsupdate script. and we can't specify "zone internal.example.com" in nsupdate script too
ZoneRunner and custom root hints
Hi, I am fighting with customizing root hints used by ZoneRunner (on VE 13.0.0HF2), I did everything according to this article Configuring a root.hint zone for use with the BIG-IP DNS system but I failed. If I paste content of the file get from link in article root hints then dig . NS @ is working. If I modify IP in any entry in db.external.named.root. (doing stop start for named and zrd after mod) like changing . 3600000 NS A.ROOT-SERVERS.NET. A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4 A.ROOT-SERVERS.NET. 3600000 AAAA 2001:503:ba3e::2:30 to . 3600000 NS A.ROOT-SERVERS.NET. A.ROOT-SERVERS.NET. 3600000 A 198.41.0.5 A.ROOT-SERVERS.NET. 3600000 AAAA 2001:503:ba3e::2:30 I am getting exactly same response to my query - no change in IP for A.ROOT-SERVERS.NET If I delete all entries and leave something like that: . 3600000 NS mydns.test.com. mydns.test.com. 3600000 A 192.168.1.254 ;A.ROOT-SERVERS.NET. 3600000 AAAA 2001:503:ba3e::2:30 then response to the same query is server failure What I am doing wrong then, or maybe it's a bug? My goal is to send all queries from LDNS to my DNS server that then should be responsible to provide answer to A query. In situation like described BIG-IP is handling recursion, sending requests to all NS in a chain (starting from root) - not what I need. Piotr
Adding a new WIP and having it placed in the correct Zone
I have a scenario where when I create a new Wide IP, it is not being put into the correct zone file. For example. 3 zones: example.com wip.example.com xwip.example.com When I create a new Wide IP, like test.wip.example.com, it is being placed into the example.com zone file!!. Is that the correct behavior? It gets more complicated as I also have 2 different views. External Internal which have their own zone files for each of the 3 zones. db.external.example.com db.internal.example.com etc Unfortuntely everything is being placed into the db.external.example.com file no matter what type of record it is...I have to manually move it. Is there a better way to do this? Also, does anyone know what the GTM uses to make it's decision on where to put new WIPs into what zone files? I know ZoneRunner is involved in that part, but I'm not sure how it is making it's zone file destiantion decision.GTM: Allow Recursion beside using zone Runner
Hi Team, I have zone "example.com", and in the zone runner i created a new MX recored "mail.example.com", and it works finely! but when i had to enable the recursion too, it didn't work as i couldn't enable both in the same time, is there any way to enable both in the same time... the ways to enable the recursion I know: > Lister Pool > Resolver profile >and allow recursion on named configuration
Why is named/zrd (named.log) reloading all the time ?
Hi, Anyone have any idea why my zrd (Zonerunner on 11.5.1) is reloading all the time ? it's frequent but not regular (2 seconds, 2 minutes, 43 seconds .. could be anything) - I can't see anything in /var/log/gtm, audit or any other logs that suggest why it's happening. It's possibly 'normal' however my 11.2.1 box does not do this. I'll open a case if needed but thought I'd check here first in case it is normal. Heres a sample of named.log .. 20-Aug-2014 17:16:19.587 general: info: received control channel command 'reload' 20-Aug-2014 17:16:19.587 general: info: loading configuration from '/config/named.conf' 20-Aug-2014 17:16:19.593 general: info: reading built-in trusted keys from file '/config/bind.keys' 20-Aug-2014 17:16:19.594 general: info: using default UDP/IPv4 port range: [1024, 65535] 20-Aug-2014 17:16:19.594 general: info: using default UDP/IPv6 port range: [1024, 65535] 20-Aug-2014 17:16:19.595 general: info: sizing zone task pool based on 181 zones 20-Aug-2014 17:16:19.601 general: info: reloading configuration succeeded 20-Aug-2014 17:16:19.601 general: info: reloading zones succeeded 20-Aug-2014 17:16:19.610 general: notice: all zones loaded 20-Aug-2014 17:16:19.610 general: notice: running 20-Aug-2014 17:16:21.585 general: info: received control channel command 'reload' 20-Aug-2014 17:16:21.585 general: info: loading configuration from '/config/named.conf' 20-Aug-2014 17:16:21.590 general: info: reading built-in trusted keys from file '/config/bind.keys' 20-Aug-2014 17:16:21.590 general: info: using default UDP/IPv4 port range: [1024, 65535] 20-Aug-2014 17:16:21.591 general: info: using default UDP/IPv6 port range: [1024, 65535] 20-Aug-2014 17:16:21.593 general: info: sizing zone task pool based on 181 zones 20-Aug-2014 17:16:21.599 general: info: reloading configuration succeeded 20-Aug-2014 17:16:21.599 general: info: reloading zones succeeded 20-Aug-2014 17:16:21.607 general: notice: all zones loaded 20-Aug-2014 17:16:21.607 general: notice: running 20-Aug-2014 17:17:10.619 general: info: received control channel command 'reload' 20-Aug-2014 17:17:10.619 general: info: loading configuration from '/config/named.conf' 20-Aug-2014 17:17:10.626 general: info: reading built-in trusted keys from file '/config/bind.keys' 20-Aug-2014 17:17:10.626 general: info: using default UDP/IPv4 port range: [1024, 65535] 20-Aug-2014 17:17:10.626 general: info: using default UDP/IPv6 port range: [1024, 65535] 20-Aug-2014 17:17:10.627 general: info: sizing zone task pool based on 181 zones 20-Aug-2014 17:17:10.633 general: info: reloading configuration succeeded 20-Aug-2014 17:17:10.633 general: info: reloading zones succeeded 20-Aug-2014 17:17:10.642 general: notice: all zones loaded 20-Aug-2014 17:17:10.643 general: notice: running 20-Aug-2014 17:17:56.650 general: info: received control channel command 'reload' 20-Aug-2014 17:17:56.650 general: info: loading configuration from '/config/named.conf' 20-Aug-2014 17:17:56.654 general: info: reading built-in trusted keys from file '/config/bind.keys' 20-Aug-2014 17:17:56.655 general: info: using default UDP/IPv4 port range: [1024, 65535] 20-Aug-2014 17:17:56.655 general: info: using default UDP/IPv6 port range: [1024, 65535] 20-Aug-2014 17:17:56.656 general: info: sizing zone task pool based on 181 zones 20-Aug-2014 17:17:56.662 general: info: reloading configuration succeeded 20-Aug-2014 17:17:56.662 general: info: reloading zones succeeded 20-Aug-2014 17:17:56.671 general: notice: all zones loaded 20-Aug-2014 17:17:56.672 general: notice: running
ZoneRunner error
Hello, There were some records added in the ZoneRunner when suddenly the issue happened with the error message for each menu as below: Global Traffice -> ZoneRunner -> Resource Record List -> Error: "01020005:3: The requested operation is not implemented yet" Global Traffice -> ZoneRunner -> Zone List -> Error: "General Error" Global Traffice -> ZoneRunner -> View List -> Error: "General Error" Global Traffice -> ZoneRunner -> Named Configuration -> Error: "Error trying to access the database." Login to the box showed that it keeps trying to re-starting zrd daemon. Checking the system log, I found this information (some names are changed): Aug 7 05:30:10 local/usf5-01 err zrd[2030]: 01150403:3: Server failure during update Aug 7 05:30:11 local/usf5-01 err zrd[2030]: 0115020b:3: Errors in config file server reload successful. zone internal.abcd.com/IN: journal rollforward failed: journal out of sync with zone. internal/internal.abcd.com./IN: out of range. zone 148.24.10.in-addr.arpa/IN: loaded serial 4. zone 140.24.10.in-addr.arpa/IN: loaded serial 10. I found this document in the KB that looks match with the issue: sol10066 (http://support.f5.com/kb/en-us/solutions/public/10000/000/sol10066.html). The recommended workaround is to delete the corresponding journal file. Questions: 1. I assume the corresponding journal file that need to be deleted is db.internal.abcd.com..jnl, correct? 2. Will there be a negative impact (service disruption) by deleting that file? Currently this box is still functioning well in answering DNS queries. 3. This box is part of the synchronization group, which consists of three boxes. Only this box which has ZoneRunner error, the other two are accessible from the GUI. Do I need to delete the same journal file in two other boxes? Again, will there be any service disruption caused by deleting the file? Thank you Raymond.
WIP aliases are not appeared in zone runner's resource records
Hi everyone, I just wondering if anybody else faced an issue described in the subject. Generally, when I add alias to wide ip the corresponding record with TTL 0 and type CNAME appeared in zone runner. But recently I noticed that this behaviour is not the same any more, some aliases are propagated into zone runner and some not. Is it a bug? Thanks!GTM - ZoneRunner - Invalid Empty Label
Currently running 11.5.1 HF6. When trying to create a new CNAME record for a current DNS zone, everytime I try to add it, I keep getting this error. I have tried all kind of combinations but keep getting the same error. The only way I can get this to work is by the CLI and that is quite annoying and should not be this hard. I know the names dont matchup but I edited out some of the information. Anyone ever see this before?Convert Zonerunner db files
We are in the process of migrating our 10.0 GTM to a new GTM running 11.4. We copied over the db files and moved the named.conf but the named.conf had errors loading. We then imported one zone via file and that worked, so we compared the db files and there is a significant formatting change. Obviously the 11.4 GTM is converting the formatting when we import via file, is there a way I can run that same conversion on the all the other db files? Then in theory I can load the named.conf file without error instead of having to manually import all of them. Or if there is an easier way I am open to suggestions. Thank you.
