Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support DNS search domain list (resolve local hostname to FQDN)

Open
#158 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
networking

Research direction

Start by reading the resolver configuration documented for /etc/resolv.conf, especially the domain and search options, and review gethostname behavior and the related issue #98. Check how the resolver currently handles short hostnames and determine the applicable Windows equivalent. Done means local short aliases resolve using the configured search/domain information, with the system hostname domain used when no explicit domain is set.

Written by the indexing model from the issue text.

Description

help wanted new feature

We should support the domain and search options listed in /etc/resolv.conf (and possibly Windows' equivalent). Additionally, we should check the system hostname if it includes a domain part if the domain is not explicitly set.

This is useful in corporate and home networks where a short local alias is often used, i.e. intranet actually resolves to intranet.example.com.

See also https://linux.die.net/man/5/resolv.conf, https://linux.die.net/man/2/gethostname, https://unix.stackexchange.com/questions/128091/no-domain-defined-in-etc-resolv-conf and #98.

I'm not currently working on this, but figured it makes sense to report here in order to track this feature request. In case anybody feels like picking this up, any input and PRs would be much appreciated 👍

Dominant language
PHP
Stars
542
Forks
62
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from reactphp/dns

All issues in reactphp/dns

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.