Route53Resolver#
Client#
- class Route53Resolver.Client#
A low-level client representing Amazon Route 53 Resolver (Route53Resolver)
When you create a VPC using Amazon VPC, you automatically get DNS resolution within the VPC from Route 53 Resolver. By default, Resolver answers DNS queries for VPC domain names such as domain names for EC2 instances or Elastic Load Balancing load balancers. Resolver performs recursive lookups against public name servers for all other domain names.
You can also configure DNS resolution between your VPC and your network over a Direct Connect or VPN connection:
Forward DNS queries from resolvers on your network to Route 53 Resolver
DNS resolvers on your network can forward DNS queries to Resolver in a specified VPC. This allows your DNS resolvers to easily resolve domain names for Amazon Web Services resources such as EC2 instances or records in a Route 53 private hosted zone. For more information, see How DNS Resolvers on Your Network Forward DNS Queries to Route 53 Resolver in the Amazon Route 53 Developer Guide.
Conditionally forward queries from a VPC to resolvers on your network
You can configure Resolver to forward queries that it receives from EC2 instances in your VPCs to DNS resolvers on your network. To forward selected queries, you create Resolver rules that specify the domain names for the DNS queries that you want to forward (such as example.com), and the IP addresses of the DNS resolvers on your network that you want to forward the queries to. If a query matches multiple rules (example.com, acme.example.com), Resolver chooses the rule with the most specific match (acme.example.com) and forwards the query to the IP addresses that you specified in that rule. For more information, see How Route 53 Resolver Forwards DNS Queries from Your VPCs to Your Network in the Amazon Route 53 Developer Guide.
Like Amazon VPC, Resolver is Regional. In each Region where you have VPCs, you can choose whether to forward queries from your VPCs to your network (outbound queries), from your network to your VPCs (inbound queries), or both.
client = session.create_client('route53resolver')
These are the available methods:
- associate_firewall_rule_group
- associate_resolver_endpoint_ip_address
- associate_resolver_query_log_config
- associate_resolver_rule
- can_paginate
- close
- create_firewall_domain_list
- create_firewall_rule
- create_firewall_rule_group
- create_outpost_resolver
- create_resolver_endpoint
- create_resolver_query_log_config
- create_resolver_rule
- delete_firewall_domain_list
- delete_firewall_rule
- delete_firewall_rule_group
- delete_outpost_resolver
- delete_resolver_endpoint
- delete_resolver_query_log_config
- delete_resolver_rule
- disassociate_firewall_rule_group
- disassociate_resolver_endpoint_ip_address
- disassociate_resolver_query_log_config
- disassociate_resolver_rule
- get_firewall_config
- get_firewall_domain_list
- get_firewall_rule_group
- get_firewall_rule_group_association
- get_firewall_rule_group_policy
- get_outpost_resolver
- get_paginator
- get_resolver_config
- get_resolver_dnssec_config
- get_resolver_endpoint
- get_resolver_query_log_config
- get_resolver_query_log_config_association
- get_resolver_query_log_config_policy
- get_resolver_rule
- get_resolver_rule_association
- get_resolver_rule_policy
- get_waiter
- import_firewall_domains
- list_firewall_configs
- list_firewall_domain_lists
- list_firewall_domains
- list_firewall_rule_group_associations
- list_firewall_rule_groups
- list_firewall_rules
- list_outpost_resolvers
- list_resolver_configs
- list_resolver_dnssec_configs
- list_resolver_endpoint_ip_addresses
- list_resolver_endpoints
- list_resolver_query_log_config_associations
- list_resolver_query_log_configs
- list_resolver_rule_associations
- list_resolver_rules
- list_tags_for_resource
- put_firewall_rule_group_policy
- put_resolver_query_log_config_policy
- put_resolver_rule_policy
- tag_resource
- untag_resource
- update_firewall_config
- update_firewall_domains
- update_firewall_rule
- update_firewall_rule_group_association
- update_outpost_resolver
- update_resolver_config
- update_resolver_dnssec_config
- update_resolver_endpoint
- update_resolver_rule
Client Exceptions#
Client exceptions are available on a client instance via the exceptions property. For more detailed instructions and examples on the exact usage of client exceptions, see the error handling user guide.
The available client exceptions are:
- AccessDeniedException
- ConflictException
- InternalServiceErrorException
- InvalidNextTokenException
- InvalidParameterException
- InvalidPolicyDocument
- InvalidRequestException
- InvalidTagException
- LimitExceededException
- ResourceExistsException
- ResourceInUseException
- ResourceNotFoundException
- ResourceUnavailableException
- ServiceQuotaExceededException
- ThrottlingException
- UnknownResourceException
- ValidationException
Paginators#
Paginators are available on a client instance via the get_paginator method. For more detailed instructions and examples on the usage of paginators, see the paginators user guide.
The available paginators are:
- ListFirewallConfigs
- ListFirewallDomainLists
- ListFirewallDomains
- ListFirewallRuleGroupAssociations
- ListFirewallRuleGroups
- ListFirewallRules
- ListOutpostResolvers
- ListResolverConfigs
- ListResolverDnssecConfigs
- ListResolverEndpointIpAddresses
- ListResolverEndpoints
- ListResolverQueryLogConfigAssociations
- ListResolverQueryLogConfigs
- ListResolverRuleAssociations
- ListResolverRules
- ListTagsForResource