Registro A
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://ipfyi.com/iframe/glossary/a-record/" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://ipfyi.com/glossary/a-record/Add a dynamic SVG badge to your README or docs.
[](https://ipfyi.com/glossary/a-record/)Use the native HTML custom element.
Definición
Un registro DNS que mapea un nombre de dominio a una dirección IPv4 (por ejemplo, example.com -> 93.184.216.34). El tipo de registro DNS más fundamental para resolver nombres de dominio a direcciones IP.
A Records and DNS Resolution
The A record is the most fundamental DNS record type, forming the final link between a human-readable name and the IPv4Internet Protocol version 4. The fourth revision of IP using 32-bit addresses (e.g., 192.168.1.1), providing approximately 4.3 billion unique addresses. Still the most widely used internet protocol despite address exhaustion. address where a server lives. When a browser resolves example.com, a DNS ResolverA server that receives DNS queries from clients and resolves domain names by querying the DNS hierarchy on their behalf. Public resolvers like 1.1.1.1 (Cloudflare) and 8.8.8.8 (Google) are widely used alternatives to ISP resolvers. ultimately returns an A record: example.com. 3600 IN A 93.184.216.34. The TTL (3600 seconds here) tells resolvers how long to cache the answer before re-querying.
A single domain can have multiple A records pointing to different IPv4Internet Protocol version 4. The fourth revision of IP using 32-bit addresses (e.g., 192.168.1.1), providing approximately 4.3 billion unique addresses. Still the most widely used internet protocol despite address exhaustion. addresses — a technique called round-robin DNS. Resolvers typically return all records and clients try them in order, providing rudimentary load distribution. However, this is not true load balancing: clients cache individual addresses and session affinity is not guaranteed.
A Records vs. CNAME Records
A records and CNAME RecordA DNS record that creates an alias from one domain name to another (e.g., www.example.com -> example.com). The alias inherits all DNS records of the target, but cannot coexist with other record types at the same name.s serve different purposes. An A record maps a name directly to an IP address. A CNAME creates an alias from one name to another name — the final resolution still ends at an A record. The root of a zone (the apex domain, e.g., example.com) cannot use a CNAME, only an A record, because the zone apex must serve SOA and NS records directly. Many DNS providers offer "ALIAS" or "ANAME" synthetic records to work around this at the apex.
A Records in Practice
Web servers, mail servers, and any internet-facing service need accurate A records. When a server's Public IP AddressA globally unique IP address assigned by an ISP that is routable on the public internet. Every device directly accessible from the internet must have a public IP address. changes — after migrating to new infrastructure — the A record must be updated and the old TTL must expire before all clients use the new address. Lowering the TTL to 60-300 seconds before a planned migration reduces the changeover window.
Use DNS Lookup to query A records for any domain. Use IP Lookup to investigate the IP an A record resolves to.