POST /api/bgptools/prefixes/dns
Price: 10 credits
List reverse (PTR) or forward DNS records within a BGP prefix
Enumerate DNS records within a BGP prefix. Reverse mode returns each IP address in the block with its PTR hostname; forward mode returns each address with the hostnames that resolve to it. For host discovery and infrastructure mapping within a network. Set `remove_autogen` in reverse mode to drop generic auto-generated PTRs (those derived from the IP itself). Accepts an IPv4 or IPv6 CIDR.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)prefix string required — IP prefix in CIDR notation whose DNS records to list (examples: "1.1.1.0/24", "8.8.8.0/24"; minLength: 1)direction string — Reverse DNS (address → PTR) or forward DNS (address → hostnames pointing at it) (default: "reverse"; one of: "reverse", "forward")remove_autogen boolean — For reverse DNS, drop auto-generated PTR records that are derived from the IP address (default: false)count integer required — Max number of DNS records to return (min: 1)@type string (default: "BgptoolsDnsRecord")address string requiredhostnames array (default: [])422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — Prefix not found Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.