Abstract: A DNS server includes one or more zones that store information, such as IP addresses, associated with domain names. These zones include a global names zone that stores data correlating host names to domain names. When a name query is received from a client device, the DNS server checks the global names zone for a record associated with the host name. If there is no record for the host name in the global names zone, then the query is answered using the DNS records found in a local copy of the authoritative zone. If there is a record for the host name in the global names zone, then the query is answered using the DNS records found in the global names zone. The IP address associated with the domain name is determined and returned to the client device.

Abstract: A method and system for implementing name challenge enabled zones is described herein. A DNS server receives an update from a client device. If the DNS server hosts an authoritative zone for the update, the DNS server determines whether there is a record for the host name. If so, then the IP address associated with the host name is determined. The IP address is compared to the source address of the client device sending the update. If the IP addresses match, then the update is accepted.

Abstract: Methods, systems, and computer program products for resolving domain name system records based on client authentication. Basing domain name resolution on client authentication provides remote clients with the convenience of domain names, without sacrificing the security of keeping potentially sensitive domain names private. An authoritative name server receives requests for domain name resolution from clients. For requests without client authentication, the authoritative name server responds that the domain name cannot be found. This response identifies the authoritative name server to the client so that the client can submit subsequent requests with client authentication. For requests with client authentication, the authoritative name server responds with the corresponding domain name addresses. Client may communicate domain name resolution requests directly to the authoritative name server or indirection, through one or more intermediate domain name servers.

Abstract: Methods, systems, and computer program products for resolving domain name system records based on client authentication. Basing domain name resolution on client authentication provides remote clients with the convenience of domain names, without sacrificing the security of keeping potentially sensitive domain names private. An authoritative name server receives requests for domain name resolution from clients. For requests without client authentication, the authoritative name server responds that the domain name cannot be found. This response identifies the authoritative name server to the client so that the client can submit subsequent requests with client authentication. For requests with client authentication, the authoritative name server responds with the corresponding domain name addresses. Client may communicate domain name resolution requests directly to the authoritative name server or indirection, through one or more intermediate domain name servers.

Abstract: A method and system for aging and scavenging resource records in a DNS database is provided. DNS resource records that are stored in a DNS database are assigned the timestamps indicating the last time the records were updated. Clients (owners of the resource records) periodically refresh timestamps of the DNS resource records that they registered using standard dynamic DNS update protocol. The DNS server then periodically searches its database for the stale records and deletes them. DNS database zone parameters and DNS server parameters are configured to define when a timestamp for a resource record may be updated, when a resource record may be scavenged (deleted) and which server may perform scavenging of a zone. A non-refresh interval follows the timestamp, a refresh interval follows the non-refresh interval and a scavengable period follows the refresh interval. During the non-refresh interval, an authorized DNS server may neither refresh nor scavenge the associated resource record.