Help4 Net
Internet routing

GeoDNS chooses an answer. BGP finds a path.

GeoDNS and BGP operate at different layers. A recursive resolver asks authoritative DNS for an address; after an address is returned, routers use BGP-derived reachability and policy to move packets toward it.

One request, two decisions

  1. Client asks a recursive resolver.
  2. Resolver asks Help4 authoritative DNS.
  3. GeoDNS policy selects an eligible address.
  4. Resolver caches that answer for its TTL.
  5. The client connects to the address.
  6. BGP-derived routing carries packets across networks.

Compare the control planes

GeoDNS seesQuery name, DNS record type, resolver source, optional EDNS Client Subnet, configured geography, health, capacity, and policy.
GeoDNS changesWhich IP address or hostname is returned and for how long it may be cached.
BGP seesIP prefixes, autonomous systems, advertisements, withdrawals, path attributes, and routing policy.
BGP changesWhich network path routers select toward an announced prefix.
Anycast doesAnnounces the same IP prefix from multiple locations; BGP policy selects a path to one announcement.

Why GeoDNS may not choose the physically nearest POP

GeoDNS and anycast together

A platform can use GeoDNS to choose among regional addresses and use anycast or ordinary BGP inside each address group. GeoDNS provides application-aware answer control; BGP provides network reachability. Neither replaces application health checks, capacity controls, or origin failover.

Important: GeoDNS cannot force every ISP to follow a geographic label, and BGP does not understand page health, sessions, cache state, or application capacity.

Terms

Recursive resolver

Fetches and caches DNS answers for clients.

Authoritative DNS

Serves the source-of-truth zone and routing policy answers.

Autonomous system

A routing domain identified by an ASN that exchanges reachability through BGP.

Prefix

An IP address block advertised or learned by routers.

RFC 4271: BGP-4 · RFC 8499: DNS Terminology