When you create a VPC using Amazon VPC, you automatically get DNS resolution within the VPC\nfrom Route 53 Resolver. By default, Resolver answers DNS queries for VPC domain names\nsuch as domain names for EC2 instances or Elastic Load Balancing load balancers.\nResolver performs recursive lookups against public name servers for all other domain\nnames.
\nYou can also configure DNS resolution between your VPC and your network over a Direct Connect or VPN connection:
\n\nForward DNS queries from resolvers on your network to Route 53 Resolver\n
\nDNS resolvers on your network can forward DNS queries to Resolver in a specified VPC. This allows your DNS resolvers\nto easily resolve domain names for Amazon Web Services resources such as EC2 instances or records in a Route 53 private hosted zone.\nFor more information, see\nHow DNS Resolvers\non Your Network Forward DNS Queries to Route 53 Resolver in the Amazon Route 53 Developer Guide.
\n\nConditionally forward queries from a VPC to resolvers on your network\n
\nYou can configure Resolver to forward queries that it receives from EC2 instances in your VPCs to DNS resolvers on your network.\nTo forward selected queries, you create Resolver rules that specify the domain names for the DNS queries that you want to forward\n(such as example.com), and the IP addresses of the DNS resolvers on your network that you want to forward the queries to.\nIf a query matches multiple rules (example.com, acme.example.com), Resolver chooses the rule with the most specific match\n(acme.example.com) and forwards the query to the IP addresses that you specified in that rule. For more information, see\nHow Route 53 Resolver\nForwards DNS Queries from Your VPCs to Your Network in the Amazon Route 53 Developer Guide.
\nLike Amazon VPC, Resolver is Regional. In each Region where you have VPCs, you can choose\nwhether to forward queries from your VPCs to your network (outbound queries), from your\nnetwork to your VPCs (inbound queries), or both.
\n\n## Installing\n\nTo install this package, use the CLI of your favorite package manager:\n\n- `npm install @aws-sdk/client-route53resolver`\n- `yarn add @aws-sdk/client-route53resolver`\n- `pnpm add @aws-sdk/client-route53resolver`\n\n## Getting Started\n\n### Import\n\nThe AWS SDK is modulized by clients and commands.\nTo send a request, you only need to import the `Route53ResolverClient` and\nthe commands you need, for example `ListResolverRulesCommand`:\n\n```js\n// ES5 example\nconst { Route53ResolverClient, ListResolverRulesCommand } = require(\"@aws-sdk/client-route53resolver\");\n```\n\n```ts\n// ES6+ example\nimport { Route53ResolverClient, ListResolverRulesCommand } from \"@aws-sdk/client-route53resolver\";\n```\n\n### Usage\n\nTo send a request:\n\n- Instantiate a client with configuration (e.g. credentials, region).\n - See [docs/CLIENTS](https://github.com/aws/aws-sdk-js-v3/blob/main/supplemental-docs/CLIENTS.md) for configuration details.\n - See [@aws-sdk/config](https://github.com/aws/aws-sdk-js-v3/blob/main/packages/config/README.md) for additional options.\n- Instantiate a command with input parameters.\n- Call the `send` operation on the client, providing the command object as input.\n\n```js\nconst client = new Route53ResolverClient({ region: \"REGION\" });\n\nconst params = { /** input parameters */ };\nconst command = new ListResolverRulesCommand(params);\n```\n\n#### Async/await\n\nWe recommend using the [await](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/await)\noperator to wait for the promise returned by send operation as follows:\n\n```js\n// async/await.\ntry {\n const data = await client.send(command);\n // process data.\n} catch (error) {\n // error handling.\n} finally {\n // finally.\n}\n```\n\n#### Promises\n\nYou can also use [Promise chaining](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises#chaining).\n\n```js\nclient\n .send(command)\n .then((data) => {\n // process data.\n })\n .catch((error) => {\n // error handling.\n })\n .finally(() => {\n // finally.\n });\n```\n\n#### Aggregated client\n\nThe aggregated client class is exported from the same package, but without the \"Client\" suffix.\n\n`Route53Resolver` extends `Route53ResolverClient` and additionally supports all operations, waiters, and paginators as methods.\nThis style may be familiar to you from the AWS SDK for JavaScript v2.\n\nIf you are bundling the AWS SDK, we recommend using only the bare-bones client (`Route53ResolverClient`).\nMore details are in the blog post on\n[modular packages in AWS SDK for JavaScript](https://aws.amazon.com/blogs/developer/modular-packages-in-aws-sdk-for-javascript/).\n\n```ts\nimport { Route53Resolver } from \"@aws-sdk/client-route53resolver\";\n\nconst client = new Route53Resolver({ region: \"REGION\" });\n\n// async/await.\ntry {\n const data = await client.listResolverRules(params);\n // process data.\n} catch (error) {\n // error handling.\n}\n\n// Promises.\nclient\n .listResolverRules(params)\n .then((data) => {\n // process data.\n })\n .catch((error) => {\n // error handling.\n });\n\n// callbacks (not recommended).\nclient.listResolverRules(params, (err, data) => {\n // process err and data.\n});\n```\n\n### Troubleshooting\n\nWhen the service returns an exception, the error will include the exception information,\nas well as response metadata (e.g. request id).\n\n```js\ntry {\n const data = await client.send(command);\n // process data.\n} catch (error) {\n const { requestId, cfId, extendedRequestId } = error.$metadata;\n console.log({ requestId, cfId, extendedRequestId });\n /**\n * The keys within exceptions are also parsed.\n * You can access them by specifying exception names:\n * if (error.name === 'SomeServiceException') {\n * const value = error.specialKeyInException;\n * }\n */\n}\n```\n\nSee also [docs/ERROR_HANDLING](https://github.com/aws/aws-sdk-js-v3/blob/main/supplemental-docs/ERROR_HANDLING.md).\n\n## Getting Help\n\nPlease use these community resources for getting help.\nWe use GitHub issues for tracking bugs and feature requests, but have limited bandwidth to address them.\n\n- Visit the [Developer Guide](https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide/welcome.html)\n or [API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/index.html).\n- Check out the blog posts tagged with [`aws-sdk-js`](https://aws.amazon.com/blogs/developer/tag/aws-sdk-js/)\n on AWS Developer Blog.\n- Ask a question on [StackOverflow](https://stackoverflow.com/questions/tagged/aws-sdk-js) and tag it with `aws-sdk-js`.\n- Join the AWS JavaScript community on [gitter](https://gitter.im/aws/aws-sdk-js-v3).\n- If it turns out that you may have found a bug, please [open an issue](https://github.com/aws/aws-sdk-js-v3/issues/new/choose).\n\nTo test your universal JavaScript code in Node.js, browser and react-native environments,\nvisit our [code samples repo](https://github.com/aws-samples/aws-sdk-js-tests).\n\n## Contributing\n\nThis client code is generated automatically. Any modifications will be overwritten the next time the `@aws-sdk/client-route53resolver` package is updated.\nTo contribute to client you can check our [generate clients scripts](https://github.com/aws/aws-sdk-js-v3/tree/main/scripts/generate-clients).\n\n## License\n\nThis SDK is distributed under the\n[Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0),\nsee LICENSE for more information.\n\n## Client Commands (Operations List)\n\n