Methods for dynamic DNS implementation and systems thereof

• US 9,843,554 B2
• Filed: 02/15/2012
• Issued: 12/12/2017
• Est. Priority Date: 02/15/2012
• Status: Active Grant

• Current Assignee: F5 Networks, Inc. (F5 Incorporated)
• Original Assignee: F5 Networks, Inc. (F5 Incorporated)
• Inventors: Thornewell, Peter M., Haworth, Jason, Smith, Ian, Thirasuttakorn, Nat
• Primary Examiner(s): ALGIBHAH, HAMZA N
• Application Number:
  US13/397,610
• Publication Number:
  US 20130212240A1
• Time in Patent Office: 2,127 Days
• Field of Search: 709223
• CPC Class Codes: H04L 61/251 between different IP versions
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]

Abstract

A method, computer readable medium, and device for dynamic DNS implementation, comprises receiving, at a network traffic management device, a first DNS response from a DNS server, wherein the first DNS response is compliant with Internet Protocol version 4 (IPv4). The first DNS response corresponds to a first DNS request from a client device being compliant with Internet Protocol version 6 (IPv6). The first DNS response is converted into a DNS second response that is compliant with IPv6, by attaching a prefix that identifies a network gateway device which is to handle receive subsequent non-DNS requests from the client device. The second DNS response is routed to the client device. Subsequent non-DNS requests from the client device that contain at least a part of the prefix allow the network traffic management device to route the non-DNS request through the designated network gateway device.

Claims

1. A method for dynamic DNS implementation, the method comprising:

receiving, by a network traffic management device, a first DNS response from a DNS server, wherein the first DNS response is compliant with Internet Protocol version 4 (IPv4), wherein the first DNS response corresponds to a DNS request received from a client device and the DNS request is compliant with Internet Protocol version 6 (IPv6);

obtaining, by the network traffic management device, from an identifier associated with each of a plurality of network gateway devices at least one of a plurality of different availability metrics associated with each of the plurality of network gateway devices upon receiving the first DNS response from the DNS server, wherein the network gateway devices comprise Network Address Translation 64 (NAT64) devices configured to facilitate communication between the client device that is IPv6 compliant and a server that is IPv4 compliant;

selecting, by the network traffic management device, based on one or more policy rules associated with the at least one of the plurality of different availability metrics, one of the network gateway devices to handle a non-DNS request from the client device;

modifying, by the network traffic management device, the first DNS response to generate a second DNS response that is compliant with IPv6, the modifying comprising at least appending a prefix to the first DNS response such that the second DNS response is in compliance with IPv6, wherein the prefix includes a network address of the selected one of the network gateway devices that will handle the non-DNS request; and

sending, by the network traffic management device, the second DNS response to the client device.

2. The method of claim 1 further comprising:

receiving, by the network traffic management device, the non-DNS request from the client device, wherein the non-DNS request includes the network address of the selected one of the network gateway devices; and

sending, by the network traffic management device, the non-DNS request to the selected one of the network gateway devices based on the network address of the selected one of the network gateway devices included in the non-DNS request.

3. The method of claim 1 further comprising:

receiving, by the network traffic management device, the DNS request from the client device, wherein the DNS request is compliant with IPv6;

converting, by the network traffic management device, the DNS request into a DNS request that is compliant with IPv4; and

sending, by the network traffic management device, the IPv4 compliant DNS request to the DNS server, wherein the DNS server is an IPv4 device.

4. The method of claim 3, wherein converting the IPv6 compliant DNS request into the IPv4 compliant DNS request further comprises removing a plurality of bits form the prefix of the IPv6 compliant DNS request.

5. The method of claim 1, wherein the at least one of the plurality of different availability metric includes a client device location metric or network topology metric and wherein the client device is an IPv6 type device and the DNS server is an IPv4 type device.

6. A non-transitory computer readable medium having stored thereon instructions for dynamic DNS implementation, comprising executable code which when executed by one or more processors, causes the one or more processors to:

receive a first DNS response from a DNS server, wherein the first DNS response is compliant with Internet Protocol version 4 (IPv4), wherein the first DNS response corresponds to a DNS request received from a client device and the DNS request is compliant with Internet Protocol version 6 (IPv6);

obtain from an identifier associated with each of a plurality of network gateway devices at least one of a plurality of different availability metrics associated with each of the plurality of network gateway devices upon receiving the first DNS response from the DNS server, wherein the network gateway devices comprise Network Address Translation 64 (NAT64) devices configured to facilitate communication between the client device that is IPv6 compliant and a server that is IPv4 compliant;

select based on one or more policy rules associated with the at least one of the plurality of different availability metrics, one of the network gateway devices to handle a non-DNS request from the client device;

modify the first DNS response to generate a second DNS response that is compliant with IPv6, the modifying comprising at least appending a prefix to the first DNS response such that the second DNS response is in compliance with IPv6, wherein the prefix includes a network address of the selected one of the network gateway devices that will handle the non-DNS request; and

send the second DNS response to the client device.

7. The non-transitory computer readable medium of claim 6, wherein the executable code when executed by the one or more processors, further causes the processors to:

receive the non-DNS request from the client device, wherein the non-DNS request includes the network address of the selected one of the network gateway devices; and

send the non-DNS request to the selected one of the network gateway devices based on the network address of the selected one of the network gateway devices included in the non-DNS request.

8. The non-transitory computer readable medium of claim 6, wherein the executable code when executed by the one or more processors, further causes the processors to:

receive the DNS request from the client device, wherein the DNS request is compliant with IPv6;

convert the DNS request into a DNS request is compliant with IPv4; and

send the IPv4 compliant DNS request to the DNS server, wherein the DNS server is an IPv4 device.

9. The non-transitory computer readable medium of claim 6, wherein the executable code when executed by the one or more processors, further causes the processors to remove a plurality of bits that at least partially form the prefix of the IPv6 compliant DNS request.

10. The non-transitory computer readable medium of claim 6, wherein the at least one of the plurality of different availability metric includes a client device location metric or network topology metric and wherein the client device is an IPv6 type device and the DNS server is an IPv4 type device.

11. A network traffic management apparatus comprising a memory comprising programmed instructions stored thereon and one or more processors configured to be capable of executing the stored programmed instructions to:

receive a first DNS response from a DNS server, wherein the first DNS response is compliant with Internet Protocol version 4 (IPv4), wherein the first DNS response corresponds to a DNS request received from a client device and the DNS request is compliant with Internet Protocol version 6 (IPv6);

obtain from an identifier associated with each of a plurality of network gateway devices at least one of a plurality of different availability metrics associated with each of the plurality of network gateway devices upon receiving the first DNS response from the DNS server, wherein the network gateway devices comprise Network Address Translation 64 (NAT64) devices configured to facilitate communication between the client device that is IPv6 compliant and a server that is IPv4 compliant;

select based on one or more policy rules associated with the at least one of the plurality of different availability metrics, one of the network gateway devices to handle a non-DNS request from the client device;

modify the first DNS response to generate a second DNS response that is compliant with IPv6, the modifying comprising at least appending a prefix to the first DNS response such that the second DNS response is in compliance with IPv6, wherein the prefix includes a network address of the selected one of the network gateway devices that will handle the non-DNS request; and

send the second DNS response to the client device.

12. The network traffic management apparatus of claim 11, wherein the one or more processor are further configured to be capable of executing the programmed instructions to:

receive the non-DNS request from the client device, wherein the non-DNS request includes the network address of the selected one of the network gateway devices; and

send the non-DNS request to the selected one of the network gateway devices based on the network address of the selected one of the network gateway devices included in the non-DNS request.

13. The network traffic management apparatus of claim 11, wherein the one or more processor are further configured to be capable of executing the programmed instructions to:

receive the DNS request from the client device, wherein the DNS request is compliant with IPv6;

convert the DNS request into a DNS request is compliant with IPv4; and

send the IPv4 compliant DNS request to the DNS server, wherein the DNS server is an IPv4 device.

14. The network traffic management apparatus of claim 11, wherein the one or more processor are further configured to be capable of executing the programmed instructions to remove a plurality of bits that at least partially form the prefix of the IPv6 compliant DNS request.

15. The network traffic management apparatus of claim 11, wherein the at least one of the plurality of different availability metric includes a client device location metric or network topology metric and wherein the client device is an IPv6 type device and the DNS server is an IPv4 type device.

16. A network traffic management system, comprising one or more traffic management apparatuses, client devices, or server devices, the network traffic management system comprising memory comprising programmed instructions stored thereon and one or more processors configured to be capable of executing the stored programmed instructions to:

receive a first DNS response from a DNS server, wherein the first DNS response is compliant with Internet Protocol version 4 (IPv4), wherein the first DNS response corresponds to a DNS request received from a client device and the DNS request is compliant with Internet Protocol version 6 (IPv6);

obtain from an identifier associated with each of a plurality of network gateway devices at least one of a plurality of different availability metrics associated with each of the plurality of network gateway devices upon receiving the first DNS response from the DNS server, wherein the network gateway devices comprise Network Address Translation 64 (NAT64) devices configured to facilitate communication between the client device that is IPv6 compliant and a server that is IPv4 compliant;

select based on one or more policy rules associated with the at least one of the plurality of different availability metrics, one of the network gateway devices to handle a non-DNS request from the client device;

modify the first DNS response to generate a second DNS response that is compliant with IPv6, the modifying comprising at least appending a prefix to the first DNS response such that the second DNS response is in compliance with IPv6, wherein the prefix includes a network address of the selected one of the network gateway devices that will handle the non-DNS request; and

send the second DNS response to the client device.

17. The network traffic management system of claim 16, wherein the one or more processors are further configured to be capable of executing the stored programmed instructions to:

receive the non-DNS request from the client device, wherein the non-DNS request includes the network address of the selected one of the network gateway devices; and

send the non-DNS request to the selected one of the network gateway devices based on the network address of the selected one of the network gateway devices included in the non-DNS request.

18. The network traffic management system of claim 16, wherein the one or more processors are further configured to be capable of executing the stored programmed instructions to:

receive the DNS request from the client device, wherein the DNS request is compliant with IPv6;

convert the DNS request into a DNS request is compliant with IPv4; and

send the IPv4 compliant DNS request to the DNS server, wherein the DNS server is an IPv4 device.

19. The network traffic management system of claim 16, wherein the one or more processors are further configured to be capable of executing the stored programmed instructions to remove a plurality of bits that at least partially form the prefix of the IPv6 compliant DNS request.

20. The network traffic management system of claim 16, wherein the at least one of the plurality of different availability metric includes a client device location metric or network topology metric and wherein the client device is an IPv6 type device and the DNS server is an IPv4 type device.