Private DNS servers

With each private DNS server, you are able to use all the functions available in premium DNS plans. For example, you can use advanced services such as dynamic DNS, secondary DNS and TTL management. In addition, your private DNS server will be managed and supported by our professional and experienced system administrators. On the other hand, you can access it via our web interface, where you can easily manage your domain name collection.

Private DNS

Create and manage zones DNS (Domain Name System) private.

Use private DNS to create private areas with domain names that you specify. You can fully manage the areas and recordings in order to provide a resolution of host name for applications carried out inside and between virtual cloud networks (VCN ) and on site or other private networks.

The private DNS also provides DNS resolution on several networks (for example, on another virtual cloud network within the same region, in another region or on an external network). Private DNS can be managed in the DNS API and the console .

Resources used in private DNS

• Private DNS zones: Private DNS zones contain DNS data accessible only from a virtual cloud network, for example private IP addresses. A private DNS area offers the same features as an internet DNS zone, but provides answers only to customers who can reach it via a virtual cloud network. Each area belongs to a unique view.
• Private DNS zone recordings: Different types of recording are supported for the Global DNS and the DNS Private. Refer to supported resources records.
• Private DNS views: A private DNS view is a set of private areas. The same zone name can be used in many views, but the area names of a view must be unique.
• Private DNS solver : a private DNS resolver dedicated to the VCN contains the configuration which serves the responses to DNS requests within the VCN. The views of the resolver determine the area and the registration data applicable to the resolution. The resolveur addresses on the resolver provide another input and another output in addition to the default input on 169.254.169.254. For more information, see private DNS resolters.
• Private DNS solver address: Use resolver address resources to configure the virtual cloud input and output. Resolver addresses use the IP addresses of the subnet in which they are created. A corresponding virtual network interface card is created for each resolver address.

• Virtual cloud network: When you create a virtual cloud network, a dedicated resolver is also automatically created.
• Subnet: A subnet within a virtual cloud network is used when creating resolver addresses. IP addresses of the subnet are used for listening and transmission of addresses.
• Network security group: You can possibly configure the list of network security groups for resolver addresses. Network security groups control incoming and outgoing traffic towards and from the resolver address.

Refer to private DNS resolve in Networking documentation for more information on VCN resources.

Protected resources

Some private DNS resources, such as areas and views, are protected. Protected resources are managed automatically by Oracle. You can display protected resources, but the modification is limited. All resolvers dedicated to a virtual cloud network are protected. Protected resources are not taken into account within the limits or service quotas.

Default views

Each resolver dedicated to a virtual cloud network has a protected default view. You can add other areas to the default view, but restrictions apply to zone names to avoid collisions with protected areas. If a resolver is deleted and its default view contains areas that are not protected, the default view is converted into a view that is not protected instead of being deleted. You can create and attach a view to a resolver in addition to the default view so that their areas can be resolved in the VCN.

Configuration and resolution

Dns

You can create a tree structure domain Complete or partial. A view can be used by any number of resolute and can share private DNS data in Virtual cloud networks Within the same region. You can use these areas for the fractional DNS because the same zone name can be used in a private area and an internet zone. Different responses can be used for public and private queries from a VCN.

The resolver listens to 169.254.169.254 by default. You can choose to define solver addresses for more inputs and outputs. A listening solver address uses an IP address for listening in the subnet specified. A transmission resolver address uses two IP addresses, one for listening and one for transmission. Before creating a resolver address, make sure that there are enough IP addresses available in the subnet. IPv6 is not supported.

Add rules to define the request logic to requests. The only type of rule supported is Forward. This rule transmits conditionally a request to a destination IP address according to the client IP address or the Qname target. The destination IP address can be intended for a site configuration, a private network or a listening resolver address in another VCN.

1. Each attached view is evaluated in order. The default view is assessed last, if it is not explicitly included in the list.
2. Resolor rules are evaluated in order.
3. The request is resolved on the internet.

For example, if a request name is included by an area in a private view and the name does not exist in the area, it returns a response Nxdomain gradual.

Virtual cloud network

The entry and exit between virtual cloud networks or between virtual cloud networks and on -site networks require connectivity. Establishing a connection may require a Local pairing gateway or a remote pairing gateway Between virtual cloud networks. The connection between a VCN and on -site networks requires FastConnect or a tunnel Ipsec (VPN IPSEC).

Virtual cloud network safety lists and all network security groups referenced must authorize the required traffic. DHCP On the security list must be activated for entry and exit, and include the IP address of the corresponding resolver address. Safety rules for listening addresses must allow entry UDP Without connection to the port of destination 53, the UDP output without connection to the Source 53 port and the entrance TCP on the port of destination 53. Safety rules for transmission addresses must authorize the UDP output without connection to the port of destination 53, the UDP input without connection to the Source 53 port and the TCP output to the Port of Destination 53.

Job case

Personalized DNS zones in a virtual cloud network

THE zones Private dns are grouped in views . All the resolute dedicated to a virtual cloud network have a default view which is automatically created. To create a personalized DNS zone which is resolved in a virtual cloud network, create the private area in the default view of the dedicated resolver, or create the area in a new view and add the latter to the list of attached views of the dedicated resolver. To obtain a detailed guide on this configuration, see Help Center – Configuration of resolters and views of private DNS zones.

Splitting

Create private areas with the same name as public names on the Internet. Then add the areas to one of the views of the resolver virtual cloud network . In the virtual cloud network, names are resolved according to the configuration of the private DNS. The same names give different answers depending on the origin of the request.

Private DNS shared DNS in a region

Virtual cloud networks of the same region can resolve each requests for their private views. For example, suppose you wanted to implement this solution with virtual cloud networks A and B. Add the default view of the dedicated virtual cloud network A to attached views of the dedicated resolver of the virtual cloud network B. Then add the default view of the dedicated resolver of the virtual cloud network B to the attached views of the dedicated resolver of the virtual cloud network A.

You can reuse the same private zone or the same set of private areas in several virtual cloud networks. This solution can reduce the duplication of the DNS configuration. Create a view and add private areas. For each virtual cloud network, add the new view to the list of attached views of the dedicated resolver of the virtual cloud network. To obtain a detailed guide on this configuration, see Help Center – Configuration of resolters and views of private DNS zones.

DNS resolution between virtual cloud networks

Send requests between virtual cloud networks using resolver addresses. Virtual cloud networks can exist in different regions. This solution requires a Local pairing gateway or a remote pairing gateway . To send traffic to the virtual cloud network A to Virtual B Network B, add a listening address to the Virtual Cloud network resolver B. Then add a transmission address to the dedicated resolver of the virtual cloud network. Create a rule on the dedicated resolver of the virtual cloud network A which transmits traffic to the address of the listening address of the virtual cloud network B via the transmission address of the virtual cloud network. To send traffic in the two directions between virtual cloud networks, add a transmission and listening resolver address to each dedicated resolver, and add a rule on each dedicated resolver. To obtain a detailed guide on this configuration, see Chronicles of the A-Team-Private DNS Implementation.

Connectivity between a virtual cloud network and on -site name servers

You can send requests between a virtual cloud network and on -site name servers in both directions. This solution requires connectivity between the virtual cloud network and the on -site network with FastConnect or a tunnel Ipsec (VPN IPSEC). To send traffic to a virtual cloud network, add a listening address to its dedicated resolver and send traffic to its address. To send traffic from a virtual cloud network, add a transmission address to its dedicated resolver as well as a rule which transmits traffic to the address server on site via the address. To obtain a detailed guide on this configuration, see Chronicles of the A-Team-Private DNS Implementation.

Advanced jobs

Virtual cloud networks can be configured for several employment cases. A single virtual cloud network can be both paired with another virtual cloud network and configured to connect to a on -site name server. The transfer can also be chained through many virtual cloud networks.

Resource records supported

The Oracle Cloud Infrastructure DNS service supports many types ofregistration resourceful. The following list provides a brief explanation of the objective of each type of registration supported for the DNS private. For the DNS Public, see the DNS public section supported resource records. Avoid entering confidential information when you provide registration data. The RFC links allow you to access additional information on the types of recording and their data structure.

Note on registration data

OIC normalizes all Rdata in the most readable format by the machine. The return presentation of the registration data may differ from their initial input.

Example :

CNAME, DNAME and MX registration types of recording types may contain absolute domain names. If the Rdata specified for one of these types of recording do not end with a point to represent the root, the point is added.

You can use different DNS libraries to normalize recording data before entering.

Programming language	Library
Go	DNS Library in Go
Java	dnsjava
Python	dnspython

Types of private DNS resource recording

A address recording used to point a host name to an IPV4 address. For more information on records A, refer to the RFC 1035 standard. AAAA Address Recording to point out a host name to an IPv6 address. For more information on AAAA recordings, see the RFC 3596 standard. CAA A CAA recording allows the holder of a domain name to indicate certification authorities authorized to issue certificates for this field. For more information on CAA recordings, see the RFC 6844 standard. CNAME A CNAME recording (canonical name) identifies the canonical name of a domain. For more information on CNAME recordings, see the RFC 1035 standard. DNAME A DNAME recording (delegation name) presents a behavior similar to that of a CNAME recording but allows you to correspond in correspondence the entire sub-arborescence of a wording with another area. For more information on DNAME recordings, see the RFC 6672 standard. MX A MX recording (email exchanger) defines the messaging server accepting emails from a domain. MX records should point to a host name. MX records should not point to a CNAME or an IP address for more information on MX records, refer to the RFC 1035 standard. Pt a ptr recording (pointer) corresponds to an IP address with a host name. This is the reverse behavior of a recording A which matches a host name with an IP address. PTR records are common in reverse DNS zones. For more information on PTR records, see the RFC 1035 standard. SRV A SRV (Localizer of Service) recording allows administrators to use several servers for the same area. For more information on SRV records, see the RFC 2782 standard. TXT A TXT recording contains a descriptive text readable to the eye. It may also include an eye -readable content for specific uses. This type of recording is commonly used for SPF and DKIM recordings which require text elements not readable to the eye. For more information on TXT recordings, see the RFC 1035 standard.

IAM strategies required

To use the private DNS, a user must be allowed to do so (through an IAM strategy). Users of the administrators group have the rights required. If a user is not part of the administrators group, a strategy such as it allows a specific group to manage the private DNS:

Allow Group to Manage Dns in Tenancy where target.dns.scope = 'private'

If you do not know the strategies, refer to introduction to current strategies and strategies. For more details on private DNS strategies, see DNS strategy reference.

Private DNS servers

Private DNS servers are entirely white DNS servers. When you get a private DNS server, it is linked to our network and to our web interface. The server will be managed and supported by our system administrators and you can manage all your areas via our web interface. Each private DNS server has included:

• All premium features – TTL management, DNS Secondary, Cloud domains, DNS Dynamic, SOA and Time Settics per hour
• Unlimited DNS zones. You can host as many DNS zones as your server can manage. It will be watched 24/7 and our team will contact you if the server limit is reached. We will provide detailed information (graphics and newspapers) of our surveillance.
• Unlimited DNS records. You can host as many DNS records as your server can manage. It will be monitored 24/7 and our team will contact you if a server limit is reached. If you need, we will provide you with detailed information (graphics and newspapers) of our surveillance.
• Only the locations you need. There is no need to have 10 private or more DNS servers, you can only buy private DNS servers than locations close to your customers.
• You can buy a private DNS server with resources that meet your needs. There is no need to pay for assistance, system administration and equipment that you don’t need.
• All private DNS servers are managed and supported by our team. All the features of our system will be deployed on your private server.
• Private DNS servers have a dedicated IP address and a recording pointer (PTR). They can be used for the DNS service in white marquee for resale.
• Our HTTP API can be used for complete integration with your system
• The delivery time is one working day

Advantages of using a private DNS server

The private DNS server has many advantages, and as soon as you start using it, you can enjoy it. We will therefore briefly present you the main and most important advantages offered by a private DNS server:

Premium DNS functions

With each private DNS server, you are able to use all the functions available in premium DNS plans. For example, you can use advanced services such as dynamic DNS, secondary DNS and TTL management. In addition, your private DNS server will be managed and supported by our professional and experienced system administrators. On the other hand, you can access it via our web interface, where you can easily manage your domain name collection.

DNS Records and DNS Zones

The advantage of a private DNS server is that it allows you to create and accommodate as many DNS areas as your server can manage it. If this is one of your main requirements, you must absolutely invest in such a server. Once the limit is reached, you will be notified and informed in detail. You can also create many and different types of DNS records. This gives you the opportunity to configure your DNS exactly as you wish.

Profitable solution

A private DNS server is an affordable and practical decision because you only pay for resources that meet your needs. You are not required to spend additional sums on features that you will not really use. In addition, your expenses only concern private DNS servers located near your customers. Thus, it perfectly meets your needs at a reasonable price!

Available locations:

• Private DNS servers in USA, TX
• Private DNS servers in USA, CA
• Private DNS servers in the USA, it
• Private DNS servers in the USA, go
• Private DNS servers in Canada
• DNS Private UK servers
• Private DNS servers in France
• Private DNS servers in Germany
• Private DNS servers in spain
• Private DNS servers in Portugal
• Private DNS servers in Netherlands
• Private DNS servers in Czech Republic
• Private DNS servers in Slovakia
• DNS private DNS servers
• DNS private servers in Romania
• DNS private servers in Bulgaria
• Private DNS servers in Turkey
• Private DNS servers in Israel
• Moldova DNS servers
• Private DNS servers in latvia
• Private DNS servers in Ukraine
• Private DNS servers in Russia
• DNS private servers in Australia
• Private DNS servers in Brazil
• Private DNS servers in Hong Kong
• Private DNS servers in South Africa

DDOS Protected locations:

• Private DNS servers in Germany
• Private DNS servers in France
• Private DNS servers in Canada
• Private DNS servers in the USA, go

Management of private DNS names for VPC termination point services

Service providers can configure private DNS names for their termination point services. When a service supplier uses an existing public DNS name as a private DNS name for its termination point service, service consumers do not need to modify applications that use the existing public name. Before you can configure a private DNS name for your termination point service, you must prove that you are the owner of the domain by verifying the property of the field.

Consideration

• A termination point service can only have one private DNS name.
• You should not create a registration for the name DNS private, so that only servers of the VPC of the consumer of the service can resolve the DNS private name.
• Private DNS names are not supported for the end -to -hand balancer termination points.
• To check a field, you must have a public host name or a public DNS supplier.
• You can check the domain of a subdomain. For example, you can check example.com, instead of has.example.com. As indicated in the RFC 1034 specification, each DNS label may include up to 63 characters and the entire domain name must not exceed a total length of 255 characters. If you add an additional subdomain, you must check the sub-domain or the domain. For example, imagine that you had a has.example.com and verified a example.com. You add now B.example.com As a private DNS name. You must check example.com Or B.example.com so that consumers of the service can use the name.

Verification of the property property

Your domain is associated with a set of domain name service records (DNS) that you manage through your DNS supplier. A TXT recording is a type of DNS recording that provides additional information on your field. It consists of a name and a value. As part of the verification process, you must add a TXT recording to the DNS server for your public domain.

Verification of the property of the domain is completed when we detect the existence of TXT recording in the DNS parameters of your domain.

After adding a recording, you can check the status of the domain verification process using the Amazon VPC console. In the navigation pane, choose Endpoint Services (termination point services). Select the termination point service and check the value of theDomaine verification statement in the tab Details (Details). If checking the domain is in progress, wait a few minutes and refresh the screen. If necessary, you can launch the verification process manually. Choose Actions, VERIFY DOMANT OWNERSHIP FOR PRIVATE DNS NAME (Check the property of the domain for the name DNS private).

The private DNS name is ready to be used by consumers of the service when the verification state is verified (checked). If the verification state changes, the new connection requests are refused, but the existing connections are not affected.

If the verification state is failed (stranded), see resolution of domain verification problems.

Obtaining the name and value

We provide you with the name and value you use in TXT recording. For example, information is available in AWS Management Console. Select the termination point service and consult Domain Verification Name (Domain verification name) and Domain Verification Value (Domain verification value) in the tab Details (Details) for the termination point service. You can also use the AWS CLI DESCRIBE-VPC-ENDPOINT-CONFIGURATIONS command to obtain information on the configuration of the private DNS name for the specified termination point service.

AWS EC2 DESCRIBE-VPC-ENDPOINT-SERVICE-CONFIGURATIONS \- VPCE-SVC-071AFFF7066E61E0 --query serviceconfigurations [*].PrivatednsNameConfiguration

Here is an exit example. You will use value and name when you create TXT recording.

[  "State": "PendingVerification", "Type": "TXT", "Value": "VPCE: L6P0ERXLTT45JEVFWOCP", "Name": "_6e86v84tqgqubxbwii1m">]

For example, suppose that your domain name is example.com and that Value and Name are indicated in the previous exit example. The following table is an example of TXT recording parameters.

We suggest that you use Name as a registration subdomain, as the basic domain name may already be used. However, if your DNS supplier does not allow DNS registration names to contain underlining lines, you can omit the “_6e86v84tqgqubwii1m” and simply use “example.com »In TXT recording.

After checking “_6e86v84tqgqubxbwii1m.example.com “, consumers of the service can use” Example.com “or a sub-domain (for example,” service.example.com “or” my.service.example.com “).

Adding a TXT recording to the DNS server in your domain

The procedure for adding TXT records to the DNS server in your field depends on the entity that provides your DNS service. Your DNS supplier can be Amazon Route 53 or another domain name recording office.

Create a recording for your public accommodated area. Use the following values:

• Below Record Type (Type of Recording), choose TXT.
• For TTL (seconds) (TTL [seconds]), enter 1800 .
• For Routing Policy (routing strategy), select Simple routing (single routing).
• For Record name (Recording name), enter the domain or the sub-domain.
• For VALUE/ROUTE TRAFFIC TO (Value/route traffic to), enter the domain verification value.

For more information, see creation of recordings using the console Amazon Route 53 developer guide.

Access your DNS supplier’s website and connect to your account. Look for the page to update DNS records in your field. Add a TXT recording with the name and value we have provided. Updating a DNS recording can take up to 48 hours, but it is often effective much earlier.

For more specific instructions, see the documentation of your DNS supplier. The following table provides links to the documentation of several current DNS suppliers. This list does not claim to be exhaustive and does not constitute a recommendation of the products or services provided by these companies.