F5 Logo MyF5
Search
  1. MyF5 Home
  2. External Monitoring of BIG-IP Systems: Implementations
  3. Common Elements for Listeners
Manual Chapter : Common Elements for Listeners

Applies To:

Show Versions Show Versions

BIG-IP APM

  • 17.1.1, 17.1.0, 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0

BIG-IP Analytics

  • 17.1.1, 17.1.0, 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0

BIG-IP Link Controller

  • 17.1.1, 17.1.0, 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0

BIG-IP LTM

  • 17.1.1, 17.1.0, 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0

BIG-IP PEM

  • 17.1.1, 17.1.0, 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0

BIG-IP AFM

  • 17.1.1, 17.1.0, 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0

BIG-IP DNS

  • 17.1.1, 17.1.0, 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0

BIG-IP ASM

  • 17.1.1, 17.1.0, 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0
Manual Chapter

Common Elements for Listeners

Create listeners to identify the DNS queries that BIG-IP DNS handles. The best practice is to create four listeners: one with an IPv4 address that handles UDP traffic, and one with the same IPv4 address that handles TCP traffic; one with an IPv6 address that handles UDP traffic, and one with the same IPv6 address that handles TCP traffic.
DNS zone transfers use TCP port
53
. If you do not configure a listener for TCP the client might receive the error:
connection refused or TCP RSTs.
The best practice is to create two listeners: one that handles UDP traffic and one that handles TCP traffic.
DNS zone transfers use TCP port
53
. If you do not configure a listener for TCP the client might receive the error:
connection refused or TCP RSTs.
  1. On the Main tab, click
    DNS
    Delivery
    Listeners
    .
    The Listeners List screen opens.
  2. On the Main tab, click
    Link Controller
    Listeners
    .
    The Listeners List screen opens.
  3. On the menu bar, click
    Load Balancing
    .
  4. Click
    Create
    .
    The Listeners properties screen opens.
  5. Click the name of the listener you want to modify.
  6. From the
    Protocol
     drop-down list, select either
    UDP
     or
    TCP
    .
    The listener uses the UDP or TCP protocol to listen for connections on the enabled VLANs. The default is UDP. Zone transfers require the TCP protocol.
  7. From the
    Listener
     list, select
    Advanced
    .
  8. In the
    Name
     field, type a unique name for the listener.
  9. In the
    Name
     column, click the name of a listener you want to modify.
  10. In the
    Description
     field, identify the listener in a unique way.
  11. From the
    State
     list, select
    Disabled
    .
  12. From the
    State
     list, select
    Enabled
    .
  13. For the Destination setting, in the
    Address
     field, type the IP address previously used by the legacy DNS server.
  14. For the Destination setting, in the
    Address
     field, type the IP address on which BIG-IP DNS listens for network traffic.
    The destination is a self IP address on BIG-IP DNS.
  15. For the Destination setting, in the
    Address
     field, type an IPv4 address on which BIG-IP DNS listens for network traffic.
  16. For the Destination setting, in the
    Address
     field, type an IPv4 address on which the BIG-IP system listens for DNS queries.
  17. For the Destination setting, in the
    Address
     field, type an IPv6 address on which BIG-IP DNS listens for network traffic.
  18. For the Destination setting, in the
    Address
     field, type the same IP address you used for your UDP listener.
  19. For the Destination setting, in the
    Address
     field, type the floating IP address of VLAN
    external
    . This is the IP address on which BIG-IP DNS listens for network traffic.
  20. For the Destination setting, in the
    Address
     field, type the IP address on which the system listens for network traffic.
  21. For the Destination setting, in the
    Address
     field, type the IP address on which the system listens for network traffic.
    For this example, type
    10.1.1.50
    .
  22. For the Destination setting, in the
    Address
     field, type the floating IP address you created previously. This allows either system in the redundant system configuration to handle DNS requests.
  23. For the Destination setting, in the
    Address
     field, type the IP address on which BIG-IP DNS listens for network traffic.
    The destination cannot be a self IP address on the system, because a listener with the same IP address as a self IP address cannot be advertised.
  24. For the Destination setting, in the
    Address
     field, type the IP address on which BIG-IP DNS listens for DNS queries.
    The destination is the IP address of a DNS server to which you want the listener to forward traffic.
    The destination must not match a self IP address on BIG-IP DNS.
  25. For the Destination setting, in the
    Address
     field, type the IP address on which BIG-IP DNS listens for access point name (APN) traffic.
    F5 Networks recommends that you assign a unique IP address, not a self IP address.
  26. For the Destination setting, in the
    Address
     field, type the self-IP address that is also the IP address of the DNS server that hosts the zone.
  27. For the Destination setting, in the
    Address
     field, type the IP address on which BIG-IP DNS listens for DNS queries.
    The destination is the IP address of a DNS server to which you want the listeners to route DNS queries.
    The destination must not match a self IP address on BIG-IP DNS.
  28. For the Destination setting, in the
    Address
     field, type the IPv4 address on which the BIG-IP system listens for DNS zone transfer requests for a zone hosted on a DNS server.
  29. For the Destination setting, in the
    Address
     field, type the IPv4 address on which the BIG-IP system listens for DNS zone transfer requests for a zone hosted on pool of DNS servers.
  30. For the Destination setting, in the
    Address
     field, type an asterisk (
    *
    ).
    Use the asterisk when you want BIG-IP DNS to not only process and respond to wide IP requests, but also to forward DNS queries to network resources, such as other DNS servers.
  31. In the
    Destination
     field, type the self IP address on which the Link Controller listens for traffic.
  32. In the
    Destination
     field, type the self IP address on which the Link Controller listens for traffic.
    For this example, type
    10.10.10.1
    .
  33. For the Destination setting, in the
    Address
     field, type the self IP address on which the Link Controller listens for traffic from ISP 1.
    For this example, type
    10.20.10.1
    .
  34. From the
    Service Port
     list, select the service port on which the system listens for connections.
  35. From the
    VLAN Traffic
     list, select one of the following options:
    All VLANs
    When you want this listener to handle traffic on all VLANs within the network segment.
    Use this option if BIG-IP DNS is handling traffic for the destination IP address locally. This option also applies when the system resides on a network segment that does not use VLANs.
    Enabled on
    When you want this listener to handle traffic on only the VLANs that you move from the
    Available
     list to the
    Selected
    list.
    Disabled on
    When you do not want this listener to handle traffic on the VLANs that you move from the
    Available
     list to the
    Selected
    list.
  36. From the
    VLAN Traffic
     list, select
    All VLANs
    .
  37. From the
    VLAN Traffic
     list, select
    Enabled on
    , and then move the VLANS for which you want this listener to handle traffic from the
    Available
     list to the
    Selected
     list.
  38. From the
    VLAN Traffic
     list, select
    Disabled on
    , and then move the VLANS for which you do not want this listener to handle traffic from the
    Available
     list to the
    Selected
     list.
  39. From the
    Source Address Translation
     list, select
    None
     when BIG-IP DNS does not use a source address translation pool for this listener.
  40. From the
    Source Address Translation
     list, select
    SNAT
    , and then, from the
    SNAT Pool
     list, select the pool BIG-IP DNS uses for source network address translation (SNAT).
  41. From the
    Source Address Translation
     list, select
    Auto Map
     when you want BIG-IP DNS to use the self IP addresses as the translation addresses.
  42. If you are using SNATs on your network, from the
    Source Address Translation
     list, select
    SNAT
    .
  43. Optional: If you are using NATs on your network, for the
    Address Translation
     setting, select the
    Enabled
     check box.
  44. For the
    Address Translation
     setting, select the
    Enabled
     check box.
  45. Optional: If you are using port translation on your network, for the
    Port Translation
     setting, select the
    Enabled
     check box.
  46. For the
    Port Translation
     setting, select the
    Enabled
     check box.
  47. For the
    Route Advertisement
     setting, select the
    Enabled
     check box.
  48. From the
    Auto Last Hop
     list, select
    Enabled
    .
  49. From the
    Auto Last Hop
     list, select
    Disabled
    .
  50. From the
    Last Hop Pool
     list, select
    None
    .
  51. From the
    Last Hop Pool
     list, select a pool.
  52. From the
    Service
     list, select
    Advanced
    .
  53. In the Service area, from the
    Protocol
     list, select either
    UDP
     or
    TCP
    .
  54. In the Service area, from the
    Protocol
     list, select
    UDP
    .
  55. In the Service area, from the
    Protocol
     list, select
    TCP
    .
  56. In the Service area, for the
    DNS Profile
     setting, select the
    dns
     profile.
    When the listener is defined from the BIG-IP LTM Virtual Server page, select the
    udp_gtm_dns
     profile.
  57. From the
    Protocol Profile (Client)
     list, select the profile you want to apply to a DNS query the listener receives from a client.
  58. From the
    Protocol Profile (Server)
     list, select a profile you want to apply to a DNS response the listener receives from a server.
  59. From the
    DNS Profile
     list, select:
    dns
    This is the default DNS profile. With the default
    dns
     profile, BIG-IP DNS forwards non-wide IP queries to the BIND server on the BIG-IP DNS system itself.
    <custom profile>
    If you have created a custom DNS profile to handle non-wide IP queries in a way that works for your network configuration, select it.
  60. In the Service area, from the
    DNS Profile
     list, accept the default profile
    dns
    .
    With the default profile BIG-IP DNS forwards non-wide IP queries to the BIND server on the system itself.
  61. In the Service area, from the
    DNS Profile
     list, select either
    dns
     or a custom DNS profile configured for DNS Express.
  62. In the Service area, from the
    DNS Profile
     list, select
    dns_zxfr
     (the custom profile you created to enable the BIG-IP system to process zone transfer requests).
  63. In the Service area, from the
    DNS Profile
     list, select the custom DNS profile with
    Zone Transfer
     enabled.
  64. In the Service area, from the
    DNS Profile
     list, select the custom DNS profile with
    Zone Transfer
     enabled, and
    Use BIND server on BIG-IP
     disabled.
  65. In the Service area, from the
    DNS Profile
     list, select a custom DNS profile configured for DNS caching.
  66. In the Service area, from the
    DNS Profile
     list, select a custom DNS profile that is associated with a DNS Logging profile.
  67. In the Service area, from the
    DNS Profile
     list, select a custom DNS profile configured with an AVR sampling rate.
  68. In the Service area, from the
    DNS Profile
     list, select the profile you created to manage IPv6 to IPv4 address mapping.
  69. From the
    Default Pool
     list, select the pool to which this listener forwards DNS queries.
  70. From the
    Default Pool
     list, select the pool to which this listener forwards DNS zone transfer requests.
  71. From the
    Default Persistence Profile
     list, select the profile that defines how this listener handles persistent connections.
  72. From the
    Fallback Persistence Profile
     list, select the profile you want BIG-IP DNS to use when it cannot use the selected
    Default Persistence Profile
    .
  73. From the
    Statistics Profile
     list, select the profile that defines how BIG-IP DNS handles iRules statistics.
  74. For the
    iRule Management
     setting, move the iRules you want to apply to this listener from the
    Available
     list to the
    Selected
     list.
  75. Click
    Finished
    .
  76. Click
    Update
    .
  77. Click
    Repeat
    .
  78. Click
    Cancel
    .
Create another listener with the same IPv4 address and configuration, but select
TCP
 from the
Protocol
 list. Then, create two more listeners, configuring both with the same IPv6 address, but one with the UDP protocol and one with the TCP protocol.
Contact Support Contact Support

Have a Question?

Support and Sales >

About F5

Education

F5 Sites

Support Tasks




©2023 F5, Inc. All rights reserved.


Trademarks Policies Privacy California Privacy Do Not Sell My Personal Information