Download the PHP package remotelyliving/php-dns without Composer

PHP-DNS: A DNS Abstraction in PHP

Use Cases

This library might be for you if:

• You want to be able to query DNS records locally or over HTTPS
• You want observability into your DNS lookups
• You want something easy to test / mock in your implementation
• You want to try several different sources of DNS truth
• You want to easily extend it or contribute to get more behavior you want!

Installation

Usage

Basic Resolvers can be found in src/Resolvers

These resolvers at the least implement the Resolvers\Interfaces\DNSQuery interface

• GoogleDNS (uses the GoogleDNS DNS over HTTPS API)
• CloudFlare (uses the CloudFlare DNS over HTTPS API)
• LocalSystem (uses the local PHP dns query function)
• Dig (Can use a specific nameserver per instance but requires the host OS to have dig installed). Based on Spatie DNS

Chain Resolver

The Chain Resolver can be used to read through DNS Resolvers until an answer is found. Whichever you pass in first is the first Resolver it tries in the call sequence. It implements the same DNSQuery interface as the other resolvers but with an additional feature set found in the Chain interface.

So something like:

That will call the GoogleDNS Resolver first, if no answer is found it will continue on to the LocalSystem Resolver. The default call through strategy is First to Find aka Resolvers\Interfaces\Chain::withFirstResults(): Chain

You can randomly select which Resolver in the chain it tries first too via Resolvers\Interfaces\Chain::randomly(): Chain Example:

The above code calls through the resolvers randomly until it finds any non empty answer or has exhausted order the chain.

Lastly, and most expensively, there is Resolvers\Interfaces\Chain::withAllResults(): Chain and Resolvers\Interfaces\Chain::withConsensusResults(): Chain All results will be a merge from all the different sources, useful if you want to see what all is out there. Consensus results will be only the results in common from source to source.

src/Resolvers/Interfaces

Cached Resolver

If you use a PSR6 cache implementation, feel free to wrap whatever Resolver you want to use in the Cached Resolver. It will take in the the lowest TTL of the record(s) and use that as the cache TTL. You may override that behavior by setting a cache TTL in the constructor.

If you do not wish to cache empty result answers, you may call through with this additional option:

Entities

Take a look in the src/Entities to see what's available for you to query by and receive.

For records with extra type data, like SOA, TXT, MX, CNAME, and NS there is a data attribute on Entities\DNSRecord that will be set with the proper type.

Reverse Lookup

This is offered via a separate ReverseDNSQuery interface as it is not common or available for every type of DNS Resolver. Only the LocalSystem Resolver implements it.

Observability

All provided resolvers have the ability to add subscribers and listeners. They are directly compatible with symfony/event-dispatcher

All events can be found here: src/Observability/Events

With a good idea of what a subscriber can do with them here: src/Observability/Subscribers

You could decide where you want to stream the events whether its to a log or somewhere else. The events are all safe to json_encode() without extra parsing.

If you want to see how easy it is to wire all this up, check out the repl bootstrap

Logging

All provided resolvers implement Psr\Log\LoggerAwareInterface and have a default NullLogger set at runtime.

Tinkering

Take a look in the Makefile for all the things you can do!

There is a very basic REPL implementation that wires up some Resolvers for you already and pipes events to sterr and stdout

make repl