DNS publication times for .es domains

Changes to the nameservers of a .es domain do not usually appear in the registry's zone straight away. Nic.es distributes the zone file in cycles and, after publication, internet providers' resolvers may still hold earlier answers in their cache. The process covers both domains directly under .es and their variants .com.es, .nom.es, .org.es, .gob.es and .edu.es.

These are two different waits:

1. Registry publication: Nic.es adds the domain's registration or the delegation change to the .es zone.
2. DNS cache: once the new delegation is published, each resolver stops using the old one when its cache expires.

Observed publication cycles

The operating schedule documented for Nic.es is:

• 02:00
• 06:00
• 10:00
• 14:00
• 18:00
• 22:00

That is six cycles a day, four hours apart, in mainland Spain time. This schedule is a guide only: Dominios.es does not currently publish an official commitment to those exact times, and its own technical information says it is working on generating the zone more often.

For example, a change saved at 10:05 will normally wait for the 14:00 cycle. Reaching that cycle does not mean every connection sees the new result at the same time: zone processing and DNS caches can still play a part.

The same cycle-based distribution can affect the initial registration of a .es, nameserver changes and information published in the parent zone, such as DNSSEC or certain glue records. It does not affect editing an A, MX, CNAME or TXT record inside a zone that is already delegated in the same way: those changes depend on the authoritative DNS provider and the record's TTL.

How to tell which stage it is at

Rather than waiting, first check where the change has stopped:

1. Query the domain's delegation directly on the .es authoritative servers.
2. If .es still returns the old nameservers, the change has not been published in the parent zone. Check when it was requested and which is the next expected cycle.
3. If .es already returns the new nameservers, Nic.es has finished publishing. From then on, differences between networks usually come down to caches, TTL or the new zone's configuration.
4. Query each new nameserver directly. If it does not answer as authoritative or does not contain the expected records, waiting longer will not fix the configuration.
5. If DNSSEC is in use, also check the DS record: keeping validation data that does not match the new zone can cause SERVFAIL even when the NS delegation is correct.

You can carry out these checks step by step in Check the propagation of DNS and IP changes.

Why a .com can seem faster

Registries do not publish every extension with the same process or at the same frequency. A delegation for a generic domain can become visible in its parent zone within a few minutes, while a .es may wait for the next Nic.es cycle. In both cases, old answers can persist afterwards because of caching; there is no single propagation time that applies to every internet provider.

References and validity

INCIBE's DNSSEC study documents that the .es zone file is distributed every four hours. The operating schedule of six slots is recorded by DonDominio, which also notes that the exact times have not been officially confirmed. Dominios.es describes its DNS platform and mentions optimising zone generation and increasing its frequency as a project.

As the registry may change this process, this guide should be reviewed if observations stop matching the cycles listed.