Auto-split DNS
View Patent ↗Automatically configuring split-DNS operation in a remote access point (RAP) connected to a network. During RAP initialization, the RAP establishes a secure tunnel to its controller. To use this tunnel, a client must obtain an IP address from the controller using DHCP. The RAP snoops the client DHCP request, obtaining the domain name. This returned domain name is used as a target suffix or pattern for split-DNS operation. Additionally, the RAP may query DNS servers for additional domains supported, and add these domains to targets for split-DNS operation.
1. A computer-implemented method, comprising:
receiving, by a computing device, a dynamic host configuration protocol (DHCP) request message;
determining whether the DHCP request message enables a DHCP response message to include a response message domain name;
receiving a DHCP response message, wherein a DHCP response message is associated with a domain name service (DNS) server and a response message domain name;
determining the response message domain name associated with the DHCP response message, wherein determining includes evaluating content of the DHCP response message;
receiving a DNS request message, wherein a DNS request message is associated with a request message domain name;
generating a combined domain name, wherein generating includes appending the response message domain name associated with the DHCP response message to the request message domain name associated with the DNS request message; and
routing the DNS request message using the combined domain name, wherein the DNS request message is routed to a DNS server associated with the DHCP response message.
2. The method of claim 1 , further comprising:
receiving an indication that the DNS request message routing failed; and
routing the DNS request message to a different DNS server using the request message domain name.
3. The method of claim 1 , further comprising:
determining a client associated with the DHCP request message, wherein determining includes evaluating content of the DHCP request message.
4. The method of claim 3 , wherein the DNS request message is routed to a DNS server associated with both the DHCP response message and the client associated with the DHCP request message.
5. A computer-implemented system, the system comprising:
one or more processors;
a display;
an input device; and
one or more non-transitory computer-readable storage mediums containing instructions configured to cause the one or more processors to perform operations including:
receiving a dynamic host configuration protocol (DHCP) request message;
determining whether the DHCP request message enables a DHCP response message to include a response message domain name;
receiving a DHCP response message, wherein a DHCP response message is associated with a domain name service (DNS) server and a response message domain name;
determining the response message domain name associated with the DHCP response message, wherein determining includes evaluating content of the DHCP response message;
receiving a DNS request message, wherein a DNS request message is associated with a request message domain name;
generating a combined domain name, wherein generating includes appending the response message domain name associated with the DHCP response message to the request message domain name associated with the DNS request message; and
routing the DNS request message using the combined domain name, wherein the DNS request message is routed to a DNS server associated with the DHCP response message.
6. The system of claim 5 , further comprising instructions configured to cause the one or more processors to perform operations including:
receiving an indication that the DNS request message routing failed; and
routing the DNS request message to a different DNS server using the request message domain name.
7. The system of claim 5 , further comprising instructions configured to cause the one or more processors to perform operations including:
determining a client associated with the DHCP request message, wherein determining includes evaluating content of the DHCP request message.
8. The system of claim 7 , wherein the DNS request message is routed to a DNS server associated with both the DHCP response message and the client associated with the DHCP request message.
9. A computer-program product tangibly embodied in a non-transitory machine-readable storage medium, including instructions configured to cause a data processing apparatus to:
receive a dynamic host configuration protocol (DHCP) request message;
determine whether the DHCP request message enables a DHCP response message to include a response message domain name;
receive a DHCP response message, wherein a DHCP response message is associated with a domain name service (DNS) server and a response message domain name;
determine the response message domain name associated with the DHCP response message, wherein determining includes evaluating content of the DHCP response message;
receive a DNS request message, wherein a DNS request message is associated with a request message domain name;
generate a combined domain name, wherein generating includes appending the response message domain name associated with the DHCP response message to the request message domain name associated with the DNS request message; and
route the DNS request message using the combined domain name, wherein the DNS request message is routed to a DNS server associated with the DHCP response message.
10. The computer-program product of claim 9 , further comprising instructions configured to cause the data processing apparatus to:
receive an indication that the DNS request message routing failed; and
route the DNS request message to a different DNS server using the request message domain name.
11. The computer-program product of claim 9 , further comprising instructions configured to cause the data processing apparatus to:
determine a client associated with the DHCP request message, wherein determining includes evaluating content of the DHCP request message.
12. The computer-program product of claim 11 , wherein the DNS request message is routed to a DNS server associated with both the DHCP response message and the client associated with the DHCP request message.