# neodevhost Setup for Pihole, AdGuard, AdAway, and DNS Filtering

> neodevhost is a frequently updated collection of ad and tracking blocklists distributed as hosts files, ad blocker rules, DNS configuration, and Clash data. It suits users who want one source in several blocking tools, but it offers no release history and does not document false-positive controls.

**neodevpro/neodevhost** —  The Powerful Friendly Uptodate AD Blocking Hosts  最新强大而友善的去广告

- Repository: https://github.com/neodevpro/neodevhost
- Website: https://neodev.team
- Stars: 1,370 · Forks: 84
- Language: Adblock Filter List
- License: MIT
- Published: 2026-10-16 · Updated: 2026-10-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/neodevpro-neodevhost

## What neodevhost Changes in a Blocking Setup

neodevhost addresses a distribution problem rather than providing a new blocking application. It collects ad and tracking domains, allowlisted domains, and domains identified as inaccessible upstream, then publishes the results in formats consumed by several blocking stacks. The intended users are people running a Pi-hole installation, AdAway, uBlock Origin, AdGuard, SmartDNS, Clash, or a conventional hosts file on Windows, Android, Linux, macOS, or OpenWrt.

The README reports 113,840 ad or tracking entries, 11,194 allowlist entries, and 5,353 inaccessible upstream domains, with an update date of 2026-10-15. These are counts stated by the project, not independently verified measurements. The repository says its lists are merged every day and has a last push dated 2026-10-15. However, there are no GitHub releases, so daily repository changes should not be confused with packaged releases with release notes or compatibility declarations.

The project aggregates material from anti-AD and 217heidai for blocking. Its allowlist draws from AnudeepND, Ultimate-Hosts-Blacklist, Energized Protection, 217heidai, oisd, blahdns, DNS Blocklists, and AWAvenue-Ads-Rule. That breadth is useful for a consolidated list, but it also means the resulting behavior depends on several upstream lists. The README does not document conflict resolution, update ordering, failure handling, or a process for reporting a domain that has been blocked incorrectly.

## Choosing the Correct neodevhost Format

The first practical decision is selecting a file based on the consumer, because a hosts file and an ad blocker filter syntax are not interchangeable. neodevhost publishes separate artifacts for Host, Adblocker, Dnsmasq, SmartDNS, Domain, and Clash formats. The README associates the Host artifact with Pi-hole, AdAway, and hBlock; the Adblocker artifact with uBlock Origin and AdGuard; and dedicated entries with Dnsmasq, SmartDNS, and Clash.

The repository also contains files named allow, allowlist, block, blocklist, deadblock, ownallowlist, and ownblocklist. The README does not map all of those filenames to supported applications or explain which are inputs, generated outputs, or auxiliary data. It only explicitly gives instructions for adding a host and whitelist file or link to an ad blocker. Users who need a precise deployment convention should therefore inspect the file syntax and the relevant installation script before relying on undocumented combinations.

A domain-only consumer may need the domain file rather than host or ad blocker syntax. Clash users need the published clash artifact. SmartDNS has a dedicated smartdns.conf, while Dnsmasq users have dnsmasq.conf. Choosing a file solely because its name contains "blocklist" risks feeding the wrong format to the application. The project provides the alternatives, but its documentation does not explain how they differ internally.

## Pihole Installation Through the Published Scripts

The README gives a Pi-hole procedure through Groupmanagement > Adlists and then invokes the repository's install.sh. The documented workflow first asks the administrator to log in to the Pi-hole web interface, open Groupmanagement > Adlists, and copy the NEODEV AD host link into Address. The terminal commands shown by the repository are:

```bash
sudo -i
sudo curl -s https://raw.githubusercontent.com/neodevpro/neodevhost/master/install.sh | bash
pihole -g
```

The README says to wait around 20 minutes, after which the NEODEV host and whitelist are imported into Pi-hole. The script is delivered directly from the master branch over the network and executed with bash. Its source is not reproduced in the README, so this article cannot confirm which Pi-hole files it edits, what validation it performs, or whether it preserves local additions. That makes review of install.sh a concrete prerequisite for an administrator who cannot accept an opaque remote change.

The documented removal path removes the NEODEV host and whitelist through Groupmanagement > Adlists and then runs:

```bash
sudo -i
sudo curl -s https://raw.githubusercontent.com/neodevpro/neodevhost/master/uninstall.sh | bash
pihole -g
```

The README again gives a wait time of around 20 minutes. It does not document rollback, backup behavior, or what happens if install.sh has already been changed after its initial execution. The presence of uninstall.sh establishes a removal mechanism, not a complete recovery plan.

## Manual Import for AdGuard, AdAway, and Other Consumers

For applications other than the documented Pi-hole script route, the README's basic procedure is short: download a file or copy its download link, add the host or whitelist file or link to the ad blocker, and update the data source. The published raw Host URL is:

```text
https://raw.githubusercontent.com/neodevpro/neodevhost/master/host
```

The README lists this file as compatible with Pi-hole, Adaway, and hBlock. For uBlock Origin or AdGuard, it identifies a separate artifact:

```text
https://raw.githubusercontent.com/neodevpro/neodevhost/master/adblocker
```

The documentation does not name exact menu paths for AdGuard or AdAway. It therefore supports the operation but not a click-by-click configuration for either product. A reader should use the application's current interface for subscription or filter-list management, select the format intended for that application, and then use the product's data-source update action. The exact control names are outside the project's documentation and should not be guessed here.

neodevhost also provides direct configuration artifacts for Dnsmasq and SmartDNS, plus a domain list and a Clash file. These are distribution choices rather than installer packages. There is no documented checksum, versioned URL, signed release, or compatibility matrix for selecting among them. Since the repository has no GitHub releases, updating a raw master-branch subscription also means accepting that the content can change without a versioned release marker.

## Daily Updates, MIT Licensing, and Upgrade Exposure

The repository states that merging occurs every day, and its last push was on 2026-10-15. That is evidence of recent project activity, but it does not establish how every upstream source is validated before inclusion. The README names upstream allowlist projects and two ad host sources, yet it does not publish a conflict policy, test procedure, or criteria for retiring an ineffective rule. Operational effort therefore includes checking whether essential services still resolve after a list refresh.

The project is licensed under MIT. That permits use and modification under the license's conditions, but this review does not interpret the license or provide legal advice. The more relevant operational issue is attribution and upgrade handling when generated lists combine contributions from multiple sources. The README does not document whether downstream users must preserve additional notices or how upstream licensing changes are surfaced.

Maintenance also requires a plan for every copied or subscribed file. Removing only the block source could leave a related allowlist in place, while removing both scripts as documented may not address lists manually imported through another application. Before an upgrade, an administrator should record which raw URLs or local files each product uses. The repository supplies uninstall.sh for its Pi-hole procedure, but it does not describe rollback for other consumers.

## Limits of a Consolidated neodevhost Filter

The largest limitation is the absence of a documented exception process. A blocking list can interfere with a login page, support system, update service, or application feature when a domain appears in a block source. neodevhost includes allowlists, and the README says the Pi-hole installer imports both the host and whitelist. That reduces the need to assemble those pieces separately, but it does not explain how to submit a broken site, how quickly a correction will appear, or whether a custom exception can coexist with daily updates.

The list is also a static artifact, not a browser extension or DNS server. Its effect depends on whether the selected consumer supports the chosen syntax, whether the consumer refreshes its data source, and whether the network path actually consumes the updated configuration. A successful download does not prove that a rule is active. Conversely, an active block list does not guarantee complete ad or tracking coverage, because the README does not describe request-level cosmetic filtering.

Pi-hole users have a documented script path. Other products receive downloadable formats but lack equally detailed application-specific instructions. For a small personal setup that uses one listed consumer, this may be an acceptable constraint. For a shared network or a service with strict availability needs, the lack of documented rollback, release packaging, and false-positive escalation is a more important concern than the stated entry count.

## Conclusion

Adopt neodevhost if you need one filter source across Pihole, AdGuard, AdAway, SmartDNS, or Clash and can verify the generated lists against your own services. Do not adopt it unchanged if you need documented releases, a rollback path, or clear false-positive handling. Before importing it, inspect the relevant list format, compare the included allowlist with services you depend on, and review install.sh because the repository does not include its contents or explain every modification made to Pihole.

## FAQ

### Which neodevhost file should I use for Pihole, AdAway, and hosts-file blocking?

The README identifies the Host format as compatible with Pihole, Adaway, and hBlock. Its raw download URL is https://raw.githubusercontent.com/neodevpro/neodevhost/master/host.

### Does neodevhost provide separate rules for AdGuard, uBlock Origin, and Clash?

Yes. The repository publishes an Adblocker format for uBlock Origin and AdGuard, along with a separate Clash file.

### How does neodevhost remove its lists from Pi-hole?

The README directs users to remove the NEODEV lists in Pi-hole under Groupmanagement > Adlists and run uninstall.sh. It then instructs the user to run pihole -g and wait around 20 minutes.

## Sources

- [Issues](https://github.com/neodevpro/neodevhost/issues)
- [License: MIT](https://github.com/neodevpro/neodevhost/blob/master/LICENSE)
- [neodevpro/neodevhost on GitHub](https://github.com/neodevpro/neodevhost)
- [Project website](https://neodev.team)
- [README](https://github.com/neodevpro/neodevhost/blob/master/README.md)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/neodevpro-neodevhost