Device and method for split DNS communications
View Patent ↗Automatically configuring split DNS operation in a wireless network device connected to a network. The wireless network device snoops one or more exchanged DHCP messages to obtain domain name(s) associated with the organization that are now used as target domain name suffix(es) for split DNS operations. For subsequent DNS queries, information within the message is analyzed to determine if the request includes a domain delimiter. If no delimiter, the DNS query message is sent to an internal DNS server that is located within an organization. If a delimiter exists, but the domain name in the message matches one of the target domain name suffixes, the DNS query message is sent to the internal DNS server as well. Otherwise, the DNS query message is routed over a different communication path.
1. A computer-implemented method, comprising:
receiving a dynamic host configuration protocol (DHCP) response message, wherein the DHCP response message is sent by a DHCP server in a private network, wherein the DHCP response message provides an Internet Protocol (IP) address to a network device, and wherein the 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 the DNS request message is sent to a DNS server to look up the IP address for a domain name, and wherein the DNS request message is associated with a request message domain name;
determining the request message domain name associated with the DNS request message, wherein determining includes evaluating content of the DNS request message;
comparing the response message domain name associated with the DHCP response message with the request message domain name associated with the DNS request message; and
routing the DNS request message, wherein the DNS request message is routed over a secure connection to the DNS server in the private network associated with the DHCP response message when the request message domain name associated with the DNS request message matches the response message domain name associated with the DHCP response message.
2. The method of claim 1 , wherein the DNS request message is routed to a different DNS server when the request message domain name of the DNS request message does not match the response message domain name associated with the DHCP response message.
3. The method of claim 1 , further comprising:
generating a list of additional domain names, wherein generating the list includes querying the DNS server;
comparing the list of additional domain names with the request message domain name associated with the DNS request message; and
routing the DNS request message to the DNS server when a domain name on the list of additional domain names matches the request message domain name the DNS request message.
4. The method of claim 1 , further comprising:
receiving a DHCP request message; and
determining whether the DHCP request message enables the DHCP response message to include the response message domain name.
5. The method of claim 1 , further comprising:
receiving a DHCP request message, wherein a DHCP request message is associated with a client; and
determining the client associated with the DHCP request message, wherein determining includes evaluating content of the DHCP request message.
6. The method of claim 5 , wherein the DNS request message is routed to the DNS server, and the DNS server is associated with both the DHCP response message and the client associated with the DHCP request message.
7. 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) response message, wherein the DHCP response message is sent by a DHCP server in a private network, wherein the DHCP response message provides an Internet Protocol (IP) address to a network device, and wherein the 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 the DNS request message is sent to a DNS server to look up the IP address for a domain name, and wherein the DNS request message is associated with a request message domain name;
determining the request message domain name associated with the DNS request message, wherein determining includes evaluating content of the DNS request message;
comparing the response message domain name associated with the DHCP response message with the request message domain name associated with the DNS request message; and
routing the DNS request message, wherein the DNS request message is routed over a secure connection to the DNS server in the private network associated with the DHCP response message when the request message domain name associated with the DNS request message matches the response message domain name associated with the DHCP response message.
8. The system of claim 7 , wherein the DNS request message is routed to a different DNS server when the request message domain name of the DNS request message does not match the response message domain name associated with the DHCP response message.
9. The system of claim 7 , further comprising instructions configured to cause the one or more processors to perform operations including:
generating a list of additional domain names, wherein generating the list includes querying the DNS server;
comparing the list of additional domain names with the request message domain name associated with the DNS request message; and
routing the DNS request message to the DNS server when a domain name on the list of additional domain names matches the request message domain name the DNS request message.
10. The system of claim 7 , further comprising instructions configured to cause the one or more processors to perform operations including:
receiving a DHCP request message; and
determining whether the DHCP request message enables the DHCP response message to include the response message domain name.
11. The system of claim 7 , further comprising instructions configured to cause the one or more processors to perform operations including:
receiving a DHCP request message, wherein a DHCP request message is associated with a client; and
determining the client associated with the DHCP request message, wherein determining includes evaluating content of the DHCP request message.
12. The system of claim 11 , wherein the DNS request message is routed to the DNS server, and the DNS server is associated with both the DHCP response message and the client associated with the DHCP request message.
13. 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) response message, wherein the DHCP response message is sent by a DHCP server in a private network, wherein the DHCP response message provides an Internet Protocol (IP) address to a network device, and wherein the 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 the DNS request message is sent to a DNS server to look up the IP address for a domain name, and wherein the DNS request message is associated with a request message domain name;
determine the request message domain name associated with the DNS request message, wherein determining includes evaluating content of the DNS request message;
compare the response message domain name associated with the DHCP response message with the request message domain name associated with the DNS request message; and
route the DNS request message, wherein the DNS request message is routed over a secure connection to the DNS server in the private network associated with the DHCP response message when the request message domain name associated with the DNS request message matches the response message domain name associated with the DHCP response message.
14. The computer-program product of claim 13 , wherein the DNS request message is routed to a different DNS server when the request message domain name of the DNS request message does not match the response message domain name associated with the DHCP response message.
15. The computer-program product of claim 13 , further comprising instructions configured to cause a data processing apparatus to:
generate a list of additional domain names, wherein generating the list includes querying the DNS server;
compare the list of additional domain names with the request message domain name associated with the DNS request message; and
route the DNS request message to the DNS server when a domain name on the list of additional domain names matches the request message domain name the DNS request message.
16. The computer-program product of claim 13 , further comprising instructions configured to cause a data processing apparatus to:
receive a DHCP request message; and
determine whether the DHCP request message enables the DHCP response message to include the response message domain name.
17. The computer-program product of claim 13 , further comprising instructions configured to cause a data processing apparatus to:
receive a DHCP request message, wherein a DHCP request message is associated with a client; and
determine the client associated with the DHCP request message, wherein determining includes evaluating content of the DHCP request message.
18. The computer-program product of claim 13 , wherein the DNS request message is routed to the DNS server, and the DNS server is associated with both the DHCP response message and the client associated with the DHCP request message.
19. The method of claim 2 , further comprising:
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.
20. The system of claim 8 , further comprising instructions configured to cause the one or more processors to perform operations including:
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.
21. The computer-program product of claim 14 , further comprising instructions configured to cause a data processing apparatus to:
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.