8 results about "DNS zone" patented technology

This application discloses a method and system for incremental data transmission in DNS zones. First, a new incremental transmission request protocol is established between the primary and secondary zone servers to enable incremental synchronization detection and incremental zone configuration return from the primary server. When the secondary zone server initiates an update request according to its local update timeout mechanism or periodic update mechanism, it follows the newly established request protocol. Then, when the primary zone server reads that the protocol type is the target protocol type, it checks whether the current primary zone server supports incremental transmission and simultaneously reads the address list of other primary zone servers. It then sequentially sends query requests to other primary zone servers to check whether they support incremental configuration synchronization, obtaining a list of primary zone servers that support incremental configuration synchronization. Finally, it returns the query results to the secondary zone server. This invention ensures that even in scenarios with multiple primary servers with different configurations, incremental synchronization can be used to complete configuration synchronization normally.

Methods, systems, and apparatuses are described herein for management of a Domain Name System (DNS) system. The system comprises numerous improvements, many related to CNAME records of the DNS. A computing device may manage authentication for a DNS using shared authentication credentials of a first authentication framework. In this manner, a wide variety of users might authenticate themselves using a first framework and use authentication credentials for a second framework to access a DNS. The computing device may further protect DNS servers from Denial of Service (DoS) attacks by bifurcating read and write requests to a DNS to different servers, such that attacks on read requests do not affect all of the DNS. The computing device may further validate DNS requests using, for example, natural language processing to avoid typographical errors inadvertently creating DNS zones.

Methods, systems, and apparatuses are described herein for management of a Domain Name System (DNS) system. The system comprises numerous improvements, many related to CNAME records of the DNS. A computing device may manage authentication for a DNS using shared authentication credentials of a first authentication framework. In this manner, a wide variety of users might authenticate themselves using a first framework and use authentication credentials for a second framework to access a DNS. The computing device may further protect DNS servers from Denial of Service (DoS) attacks by bifurcating read and write requests to a DNS to different servers, such that attacks on read requests do not affect all of the DNS. The computing device may further validate DNS requests using, for example, natural language processing to avoid typographical errors inadvertently creating DNS zones.

Methods, systems, and apparatuses are described herein for management of a Domain Name System (DNS) system. The system comprises numerous improvements, many related to CNAME records of the DNS. A computing device may manage authentication for a DNS using shared authentication credentials of a first authentication framework. In this manner, a wide variety of users might authenticate themselves using a first framework and use authentication credentials for a second framework to access a DNS. The computing device may further protect DNS servers from Denial of Service (DOS) attacks by bifurcating read and write requests to a DNS to different servers, such that attacks on read requests do not affect all of the DNS. The computing device may further validate DNS requests using, for example, natural language processing to avoid typographical errors inadvertently creating DNS zones.

Systems, methods and devices are provided for registering DNS hostnames of Internet host devices for very large domain zones (VLZ) stored on a DNS server on a network, including setting a pseudo-zone as the VLZ, intercepting DNS updates to the pseudo-zone, mapping the entries in the pseudo-zone into a hierarchy of real parent zones and sub-zones using a mapping formula, and translating DNS updates to the pseudo-zone from an original fully qualified domain name (FQDN) into a at least one new FQDNs and adding the at least one new FQDNs to an authoritative DNS Server.

Techniques for creating a custom endpoint for a cloud application instance are disclosed. In some embodiments, a system receives a user request to enable a custom endpoint to be used to access a cloud application instance. In response to the user request, the system validates the custom endpoint in a Domain Name System (DNS) zone of a customer tenancy of a cloud platform in which the cloud application instance is hosted, obtains a security token of the cloud application instance from the customer tenancy, creates a DNS record in the DNS zone using the security token, obtains a digital certificate for the custom endpoint using the DNS record, and creates an association between the digital certificate and the custom endpoint on the cloud platform, wherein the association between the digital certificate and the custom endpoint enables access to the cloud application instance via the custom endpoint.

Methods, systems, and apparatuses are described herein for management of a Domain Name System (DNS) system. The system comprises numerous improvements, many related to CNAME records of the DNS. A computing device may manage authentication for a DNS using shared authentication credentials of a first authentication framework. In this manner, a wide variety of users might authenticate themselves using a first framework and use authentication credentials for a second framework to access a DNS. The computing device may further protect DNS servers from Denial of Service (DoS) attacks by bifurcating read and write requests to a DNS to different servers, such that attacks on read requests do not affect all of the DNS. The computing device may further validate DNS requests using, for example, natural language processing to avoid typographical errors inadvertently creating DNS zones.

A method for creating an infrastructure for a plurality of cloud providers includes receiving input data corresponding to the infrastructure for the plurality of cloud providers. The input data includes a plurality of deployments, a DNS zone including a single DNS name, and a global load balancer. The method also includes modifying a terraform configuration file based on the input data to define the infrastructure and thereby improve a distribution across the plurality of cloud providers. Modifying the terraform configuration file includes defining a respective path and respective deployment rules for each deployment of the plurality of deployments, defining the DNS zone and the single DNS name thereof, and defining one or more routing rules for the global load balancer. The method also includes creating the infrastructure based on the terraform configuration file to provide enhanced resiliency across the plurality of cloud providers.