Skip to main content
We’ve updated our Terms of Service. A new AI Addendum clarifies how Stack Overflow utilizes AI interactions.
Server Fault

Return to Answer

clarified, added info from comments
Source Link
Tim
Tim
  • 33.9k
  • 7
  • 58
  • 84

As described by AWS the .2VPC base address plus two of your CIDR is a DNS server - eg if the DNS serverVPC is 192.168.5.0 it's 192.168.5.2. This is likely to be youra suitable resolver.

As Michael has pointed out in the comments 169.254.169.253 is a DNS resolver with a static IP, so it's easier to port across VPCs. That's one IP below the user metadata IP.

You haven't really described exactly what problem you're having, so it's difficult to give you any more advice.

  • 10.0.0.0: Network address.
  • 10.0.0.1: Reserved by AWS for the VPC router.
  • 10.0.0.2: Reserved by AWS. The IP address of the DNS server is always the base of the VPC network range plus two; however, we also reserve the base of each subnet range plus two. For VPCs with multiple CIDR blocks, the IP address of the DNS server is located in the primary CIDR. For more information, see Amazon DNS Server.
  • 10.0.0.3: Reserved by AWS for future use.
  • 10.0.0.255: Network broadcast address. We do not support broadcast in a VPC, therefore we reserve this address.

As described by AWS the .2 of your CIDR is the DNS server. This is likely to be your resolver.

You haven't really described exactly what problem you're having, so it's difficult to give you any more advice.

  • 10.0.0.0: Network address.
  • 10.0.0.1: Reserved by AWS for the VPC router.
  • 10.0.0.2: Reserved by AWS. The IP address of the DNS server is always the base of the VPC network range plus two; however, we also reserve the base of each subnet range plus two. For VPCs with multiple CIDR blocks, the IP address of the DNS server is located in the primary CIDR. For more information, see Amazon DNS Server.
  • 10.0.0.3: Reserved by AWS for future use.
  • 10.0.0.255: Network broadcast address. We do not support broadcast in a VPC, therefore we reserve this address.

As described by AWS the VPC base address plus two of your CIDR is a DNS server - eg if the VPC is 192.168.5.0 it's 192.168.5.2. This is likely a suitable resolver.

As Michael has pointed out in the comments 169.254.169.253 is a DNS resolver with a static IP, so it's easier to port across VPCs. That's one IP below the user metadata IP.

You haven't really described exactly what problem you're having, so it's difficult to give you any more advice.

  • 10.0.0.0: Network address.
  • 10.0.0.1: Reserved by AWS for the VPC router.
  • 10.0.0.2: Reserved by AWS. The IP address of the DNS server is always the base of the VPC network range plus two; however, we also reserve the base of each subnet range plus two. For VPCs with multiple CIDR blocks, the IP address of the DNS server is located in the primary CIDR. For more information, see Amazon DNS Server.
  • 10.0.0.3: Reserved by AWS for future use.
  • 10.0.0.255: Network broadcast address. We do not support broadcast in a VPC, therefore we reserve this address.
Source Link
Tim
Tim
  • 33.9k
  • 7
  • 58
  • 84

As described by AWS the .2 of your CIDR is the DNS server. This is likely to be your resolver.

You haven't really described exactly what problem you're having, so it's difficult to give you any more advice.

  • 10.0.0.0: Network address.
  • 10.0.0.1: Reserved by AWS for the VPC router.
  • 10.0.0.2: Reserved by AWS. The IP address of the DNS server is always the base of the VPC network range plus two; however, we also reserve the base of each subnet range plus two. For VPCs with multiple CIDR blocks, the IP address of the DNS server is located in the primary CIDR. For more information, see Amazon DNS Server.
  • 10.0.0.3: Reserved by AWS for future use.
  • 10.0.0.255: Network broadcast address. We do not support broadcast in a VPC, therefore we reserve this address.