Weave Code
Net Dns2 Laravel Package
pear/net_dns2
Net_DNS2 is a pure-PHP DNS resolver for querying A, AAAA, MX, NS, TXT, SRV, SOA and other records over UDP or TCP. It supports IPv4/IPv6, custom nameservers, caching, and detailed response objects, so PHP apps can perform DNS lookups without external extensions.
PHP DNS Resolver and Updater
Frequently asked questions about Net Dns2
- Is pear/net_dns2 a Laravel package?
- No. pear/net_dns2 is a low-level, synchronous PHP DNS resolver rather than a Laravel package. It does not provide service providers, facades, config publishing, queue integration, caching, or Laravel testing helpers. In Laravel, treat it as an infrastructure adapter behind an application-owned interface.
- How do I install pear/net_dns2 in a Laravel application?
- Install it with Composer using pear/net_dns2. Because the library uses PEAR-style class names such as Net_DNS2_*, you may need explicit classmap or autoload handling instead of assuming PSR-4 behavior. After installation, bind a wrapper service in the container rather than using Net_DNS2_* classes directly in controllers or domain logic.
- Which DNS record types can pear/net_dns2 query?
- It can query common record types including A, AAAA, MX, NS, TXT, SRV, SOA, and CNAME. It supports lookups over UDP or TCP and returns detailed response objects. That coverage fits most Laravel use cases such as domain verification, email checks, and DNS health monitoring.
- Does pear/net_dns2 support custom nameservers, IPv4, and IPv6?
- Yes. The library supports IPv4 and IPv6 and allows custom nameservers. It also supports caching and detailed response objects so your application can inspect DNS answers and errors. You should still expose nameserver and timeout settings through Laravel configuration rather than hard-coding them.
- How should I integrate pear/net_dns2 into Laravel architecture?
- Define an application contract such as App\Contracts\DnsResolver with methods like resolveA, resolveMx, and resolveTxt. Implement a NetDns2Resolver adapter behind that contract, bind it in AppServiceProvider, and return application-specific result objects instead of raw Net_DNS2_* responses. Add config/dns.php for nameservers, timeouts, retries, cache TTL, and allow-list or deny-list behavior.
- Can I use pear/net_dns2 for domain verification and email validation in Laravel?
- Yes. It is suitable for custom-domain verification, MX, SPF, DKIM, and DMARC checks, tenant onboarding, and scheduled DNS record-drift monitoring. Because DNS calls are blocking, run these checks in queued jobs where possible. Add caching, strict timeouts, and fallback behavior before using them in user-facing workflows.
- What are the timeout and blocking I/O concerns with pear/net_dns2?
- The resolver is synchronous and can block PHP-FPM or queue workers if DNS is slow or unreachable. Wrap it with strict timeouts, retries, caching, and fallback behavior. Avoid placing live DNS lookups on request-critical paths unless you have measured and controlled the latency.
- How do I test pear/net_dns2 DNS lookups without live network calls in CI?
- The package does not provide Laravel testing helpers, so mock your own DnsResolver interface or adapter in unit and feature tests. Return deterministic fake DNS results and errors rather than making real network calls. Keep a small integration test or time-boxed spike for validating actual package behavior separately.
- What security risks come with user-supplied domains in pear/net_dns2?
- User-supplied domains can enable SSRF-like DNS probing, internal-name resolution, and abuse of outbound DNS traffic. Normalize domains, enforce allow-lists or deny-lists, apply rate limits, and restrict what internal names can be resolved. Treat DNS lookups as untrusted external calls and log abusive patterns.
- Is pear/net_dns2 maintained enough for production Laravel apps, and what are the alternatives?
- It has a low star count, zero dependents, and a PEAR-era codebase, so validate PHP 8.x and Laravel 10, 11, or 12 compatibility before adopting it. Start with a time-boxed spike in a non-critical workflow and keep the adapter replaceable. Maintain a fallback implementation using PHP's dns_get_record, a fork, or a more actively maintained resolver behind the same interface.
Weaver
How can I help you explore Laravel packages today?