For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

dstogsdill_2492's avatar
dstogsdill_2492
Icon for Nimbostratus rankNimbostratus
Nov 04, 2012

GTM iRule - cname

Hi all,   I'm trying to test a simple iRule to return a cname for a wide IP. I looked at the cname Wiiki on dev central and my syntax looks correct, however, it is not returning the cname respons...
application delivery
dev
devops
iRules
Mudhen_64776's avatar
Mudhen_64776
Icon for Nimbostratus rankNimbostratus
Sep 12, 2018

Anyone happen to have duplicated the AWS/EAV/iRule configuration on v12+?

 

I got it running on v11 but v13 is so very different (and just running an upgrade only brings in the objects, it breaks it completely)...like you can't apply an EAV to a CNAME pool. And if you use an 'A' record pool you can't have a CNAME.

 

Even in my iRule if I try to tell it to return the CNAME pool it doesn't work - as soon as you use the keyword 'cname' it returns the next entry as the CNAME itself, not the pool. And if you don't use the keyword 'cname' it says it can't find the CNAME pool. lol.

 

Thx

 

  • Mudhen_64776's avatar
    Mudhen_64776
    Icon for Nimbostratus rankNimbostratus
    Sep 12, 2018

    Nm...got it. Use an 'A' record pool and if it returns 'up' from the EAV have the iRule respond directly with the CNAME, don't have it attempt to point to a pool to return the CNAME. Bazinga.

     

    v13 is a four letter word.

     

    M

     

    • anonomike's avatar
      anonomike
      Icon for Nimbostratus rankNimbostratus
      Mar 07, 2020

      This is the closest thread I can find to my issue: 13.1.1 and Applications are moving into Azure. All that is supposed to be required is CNAME to Azure's CNAMEs but although this works on the external BIG-IP DNS with ZoneRunner something is not working with internal DNS Express which is getting it's records of a Windows server

       

      The results look fine from a dig but no web access - Not FW as the browser responds with resolution error

       

      $ dig @internal1 tst.wa.au q-opt any

       

      ; <<>> DiG 9.11.4-P2-RedHat-9.11.4-9.P2.el7 <<>> @internal1 tst.wa.au q-opt any

       

      ; (1 server found)

       

      ;; global options: +cmd

       

      ;; Got answer:

       

      ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57169

      ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

      ;; WARNING: recursion requested but not available

       

      ;; OPT PSEUDOSECTION:

       

      ; EDNS: version: 0, flags:; udp: 4096

       

      ;; QUESTION SECTION:

       

      tst.wa.au IN A

       

      ;; ANSWER SECTION:

       

      tst.wa.au 3600 IN CNAME aut.azurewebsites.net.

       

      ;; Query time: 4 msec

       

      ;; SERVER: 172.30.96.220#53(172.30.96.220)

       

      ;; WHEN: Sat Mar 07 16:04:30 AWST 2020

       

      ;; MSG SIZE rcvd: 117

       

      ;; Got answer:

       

      ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22006

       

      ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

       

      ;; OPT PSEUDOSECTION:

       

      ; EDNS: version: 0, flags:; udp: 4096

       

      ;; QUESTION SECTION:

       

      ;q-opt.       IN  ANY

       

       

      ;; AUTHORITY SECTION:

       

      .      15  IN  SOA  a.root-servers.net. nsld.veign-grs.com. 2020030700 1800 900 604800 86400