Help
The lookup asks Lazco's own resolver for one name and one record type and shows its answer, so you can check what the world sees for a domain and share it with one link.
How the lookup works
The resolver runs in Lazco's network and resolves every name from the root servers itself, with no other resolver in between. It validates DNSSEC signatures, asks each server for no more of the name than it needs, and keeps answers only for their TTL.
No queried name and no visitor address is stored or logged.
Reading an answer
Status- The response code: 0 NOERROR, 2 SERVFAIL, 3 NXDOMAIN, 5 REFUSED.
TC, RD, RA- The flags of the answer: truncated, recursion desired and recursion available.
AD- True when the resolver validated the answer with DNSSEC. False for a domain that is not signed.
CD- True when DNSSEC validation was disabled for the query, so a domain with a broken signature still answers.
Question- The name and type that were asked. A type is shown by its number, with its name beside it on the page.
Answer, Authority- The records, each with its name, type, time to live in seconds and data. The authority section holds the zone's SOA when the name or type does not exist.
Comment- A note from the lookup, such as a resolver timeout.
JSON API
Every answer is also available as JSON, in the same format as the JSON APIs of large public resolvers. Send a GET request:
GET https://dns.lazco.tw/resolve?name=example.com&type=NS
name: the domain name or IP address. Required.type: the record type, by name or number. A by default.cd: 1 to disable DNSSEC validation.do: 1 to include the DNSSEC records.
The page and the API together answer 10 queries a minute per address, with bursts of up to 20. Over that, the answer is 429 with a Retry-After header, and the RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers show what is left. ANY, AXFR and other meta types are not offered.
Cache flush
After a change, resolvers keep the old records until their TTL expires. This lookup has its own cache too, which follows the same TTL.
Large public resolvers offer a page that asks them to drop their cached records of a domain:
Get started
Zones are created in the Lazco console. Create the zone there first and add its records, and only then change the nameservers at the registrar. Until the zone exists, Lazco DNS has no records to answer for the domain.
At the registrar, set the domain's nameservers to these names, the names only:
ns1.lazco.twns2.lazco.tw
If the parent zone publishes a DS record for the domain, remove it, or turn DNSSEC off at the registrar, before you change the nameservers. That DS matches the previous host's key, so while it stays, validating resolvers stop resolving the domain.
Lazco DNS signs a zone once DNSSEC is turned on for it, with algorithm 13 (ECDSA P-256 with SHA-256), and not before. After the nameserver change, an owner or an admin of the organization turns DNSSEC on from the zone's page in the Lazco console, then adds at the registrar the DS record that appears there within the hour.
Contact
- Report abuse: abuse@lazco.tw
- Report a vulnerability: security@lazco.tw
- Everything else: support@lazco.tw
Not sure which address to use? Write to support@lazco.tw.