# US 2013/0254423 A1 · Use of dns information as trigger for dynamic ipv4 address allocation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0254423 A1
- Document ID: US20130254423A1
- Status: Published application
- Kind: A1
- Application number: 13/427,606
- Filed: 2012-03-22
- Published: 2013-09-26
- Earliest claimed: 2012-03-22
- Assignees: Time Warner Cable Inc.
- Inventors: Wesley E. George, IV
- Web page: https://patentgrep.com/patent/US20130254423A1

## CPC

- H04L 61/4511: using domain name system [DNS]
- H04L 61/00: Network arrangements, protocols or services for addressing or naming
- H04L 61/2514: between local and global IP addresses
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A first request, to access a web site associated with a domain name, is obtained at a gateway router interposed between a local area network and an internet service provider's infrastructure, from a host on the local area network. The gateway router has Domain Name Service (DNS) resolver capability. The first request is received while the gateway router has upstream connectivity to the internet service provider's infrastructure via IPv6 but not via IPv4. Further steps include sending, from the gateway router, the first request; obtaining, at the gateway router, an indication that an IPv4 address will imminently be required for the gateway router; and, responsive to obtaining the indication, sending, from the gateway router, into the internet service provider's infrastructure, a second request, for an IPv4 address for the gateway router.

## Claims

### Claim 1

A method comprising the steps of:
obtaining, at a gateway router interposed between a local area network and an internet service provider's infrastructure, from a host on said local area network, a first request, said first request being to access a web site associated with a domain name, said gateway router having Domain Name Service (DNS) resolver capability, said first request being received while said gateway router has upstream connectivity to said internet service provider's infrastructure via Internet Protocol Version 6 (IPv6) but not via Internet Protocol Version 4 (IPv4);
sending, from said gateway router, said first request;
obtaining, at said gateway router, an indication that an Internet Protocol Version 4 (IPv4) address will imminently be required for said gateway router; and
responsive to obtaining said indication, sending, from said gateway router, into said internet service provider's infrastructure, a second request, said second request being for an Internet Protocol Version 4 (IPv4) address for said gateway router.

### Claim 2 (depends on 1)

The method of claim 1, wherein said indication comprises an indication that said domain name resolves to an Internet Protocol Version 4 (IPv4) address.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
obtaining, at said gateway router, said Internet Protocol Version 4 (IPv4) address for said gateway router;
obtaining, at said gateway router, from said host on said local network, a third request, said third request being to connect to said Internet Protocol Version 4 (IPv4) address to which said domain name resolves; and
processing said third request, by said gateway router, using said Internet Protocol Version 4 (IPv4) address for said gateway router obtained in said step of obtaining said Internet Protocol Version 4 (IPv4) address for said gateway router.

### Claim 4 (depends on 3)

The method of claim 3, wherein, in said step of obtaining said first request, said first request comprises a fully qualified domain name (FQDN).

### Claim 5 (depends on 3)

The method of claim 3, wherein, in said step of obtaining said indication that said domain name resolves to said Internet Protocol Version 4 (IPv4) address, said indication comprises an A-record.

### Claim 6 (depends on 3)

The method of claim 3, wherein, in said step of obtaining said indication that said domain name resolves to said Internet Protocol Version 4 (IPv4) address, said indication comprises an indication that said domain name resolves solely to said Internet Protocol Version 4 (IPv4) address.

### Claim 7 (depends on 6)

The method of claim 6, wherein said indication that said domain name resolves solely to said Internet Protocol Version 4 (IPv4) address comprises an A-record obtained without a quad-A record.

### Claim 8 (depends on 6)

The method of claim 6, further comprising:
obtaining, at said gateway router, from another host on said local area network, a fourth request, said fourth request being to access another web site associated with another domain name, said fourth request being received while said gateway router has said upstream connectivity to said internet service provider's infrastructure via said Internet Protocol Version 6 (IPv6) but not via said Internet Protocol Version 4 (IPv4);
sending, from said gateway router, to said domain name server of said internet service provider's infrastructure, said fourth request;
obtaining, at said gateway router, an indication that said other domain name resolves to both an Internet Protocol Version 4 (IPv4) address and an Internet Protocol Version 6 (IPv6) address; and
responsive to said indication that said other domain name resolves to both said Internet Protocol Version 4 (IPv4) address and said Internet Protocol Version 6 (IPv6) address, accessing said other web site via Internet Protocol Version 6 (IPv6).

### Claim 9 (depends on 1)

The method of claim 1, wherein, in said step of obtaining said first request, said first request is made in Internet Protocol Version 6 (IPv6).

### Claim 10 (depends on 1)

The method of claim 1, wherein in said step of obtaining said first request, said first request is made in Internet Protocol Version 4 (IPv4), further comprising translating said first request into Internet Protocol Version 6 (IPv6) at said gateway router, wherein, in said step of sending said first request, said first request is sent in Internet Protocol Version 6 (IPv6).

### Claim 11 (depends on 1)

The method of claim 1, further comprising providing a system, wherein said system comprises distinct software modules, each of said distinct software modules being embodied on at least one tangible computer readable recordable storage medium, and wherein said distinct software modules comprise a DNS client/server module and a DHCP client/server module;
wherein:
said obtaining of said first request is carried out by said DNS client/server module executing on at least one hardware processor of said gateway router;
said sending of said first request is carried out by said DNS client/server module executing on said at least a one hardware processor of said gateway router;
said obtaining of said indication is carried out by said DNS client/server module executing on said at least a one hardware processor of said gateway router; and
said sending of said second request is carried out by said DHCP client/server module executing on said at least a one hardware processor of said gateway router.

### Claim 12 (depends on 1)

The method of claim 1, wherein said first request is sent to a domain name server of said internet service provider's infrastructure.

### Claim 13 (depends on 1)

The method of claim 1, wherein said first request is sent to a root server associated with said domain name.

### Claim 14

A gateway router for interposition between a local area network and an internet service provider's infrastructure, said gateway router comprising:
a memory storing in a non-transitory manner a plurality of distinct software modules, said distinct software modules comprising a DNS client/server module and a DHCP client/server module; and
at least one processor, coupled to said memory;
wherein:
said DNS client/server module comprises instructions configured to cause said at least one processor to:
obtain, from a host on said local area network, a first request, said first request being to access a web site associated with a domain name, said gateway router having Domain Name Service (DNS) resolver capability;
send, to a domain name server of said internet service provider's infrastructure, said first request; and
obtain an indication that an Internet Protocol Version 4 (IPv4) address will imminently be required for said gateway router; and
said DHCP client/server module comprises instructions configured to cause said at least one processor to, responsive to obtaining said indication, send, into said internet service provider's infrastructure, a second request, said second request being for an Internet Protocol Version 4 (IPv4) address for said gateway router.

### Claim 15 (depends on 14)

The gateway router of claim 14, wherein said indication comprises an indication that said domain name resolves to an Internet Protocol Version 4 (IPv4) address.

### Claim 16 (depends on 15)

The gateway router of claim 15, wherein said at least one processor is further operative to:
obtain said Internet Protocol Version 4 (IPv4) address for said gateway router;
obtain, from said host on said local network, a third request, said third request being to connect to said Internet Protocol Version 4 (IPv4) address to which said domain name resolves; and
process said third request, by said gateway router, using said obtained Internet Protocol Version 4 (IPv4) address for said gateway router.

### Claim 17

An article of manufacture comprising a computer program product, said computer program product comprising:
a tangible computer-readable recordable storage medium, storing in a non-transitory manner computer readable program code, the computer readable program code comprising:
computer readable program code configured to obtain, from a host on said local area network, a first request, said first request being to access a web site associated with a domain name, said gateway router having Domain Name Service (DNS) resolver capability, said first request being received while said gateway router has upstream connectivity to said internet service provider's infrastructure via Internet Protocol Version 6 (IPv6) but not via Internet Protocol Version 4 (IPv4);
computer readable program code configured to send said first request;
computer readable program code configured to obtain an indication that an Internet Protocol Version 4 (IPv4) address will imminently be required for said gateway router; and
computer readable program code configured to, responsive to obtaining said indication, send, into said internet service provider's infrastructure, a second request, said second request being for an Internet Protocol Version 4 (IPv4) address for said gateway router.

### Claim 18 (depends on 17)

The article of manufacture of claim 17, wherein said indication comprises an indication that said domain name resolves to an Internet Protocol Version 4 (IPv4)) address.

### Claim 19 (depends on 18)

The article of manufacture of claim 18, further comprising:
computer readable program code configured to obtain said Internet Protocol Version 4 (IPv4) address for said gateway router;
computer readable program code configured to obtain, from said host on said local network, a third request, said third request being to connect to said Internet Protocol Version 4 (IPv4) address to which said domain name resolves; and
computer readable program code configured to process said third request, by said gateway router, using said obtained Internet Protocol Version 4 (IPv4) address for said gateway router.

### Claim 20

An apparatus comprising:
means for obtaining, at a gateway router interposed between a local area network and an internet service provider's infrastructure, from a host on said local area network, a first request, said first request being to access a web site associated with a domain name, said gateway router having Domain Name Service (DNS) resolver capability, said first request being received while said gateway router has upstream connectivity to said internet service provider's infrastructure via Internet Protocol Version 6 (IPv6) but not via Internet Protocol Version 4 (IPv4);
means for sending, from said gateway router, said first request;
means for obtaining, at said gateway router, an indication that an Internet Protocol Version 4 (IPv4) address will imminently be required for said gateway router; and
means, responsive to obtaining said indication, for sending, from said gateway router, into said internet service provider's infrastructure, a second request, said second request being for an Internet Protocol Version 4 (IPv4) address for said gateway router.

### Claim 21

A method comprising the steps of:
obtaining, at a network address translation module of a gateway router, a request from a local host for a universal plug and play port mapping on Internet Protocol Version 4 (IPv4); and
responsive to obtaining said request, sending, from said gateway router, into an infrastructure of an internet service provider, a request for an Internet Protocol Version 4 (IPv4) address for said gateway router.

### Claim 22 (depends on 21)

The method of claim 21, further comprising providing a system, wherein said system comprises distinct software modules, each of said distinct software modules being embodied on at least one tangible computer readable recordable storage medium, and wherein said distinct software modules comprise a network address translation module and a DHCP client/server module;
wherein:
said obtaining of said request is carried out by said network address translation module executing on at least one hardware processor of said gateway router; and
said sending of said request is carried out by said DHCP client/server module executing on said at least a one hardware processor of said gateway router.
