this post was submitted on 21 Jun 2024
22 points (89.3% liked)

Selfhosted

39921 readers
371 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
22
DNS issues (feddit.it)
submitted 4 months ago* (last edited 2 months ago) by Shimitar@feddit.it to c/selfhosted@lemmy.world
9 comments fedilink hide all child comments
 

Hi! i am selfhosting my services and using a DNSMasq setup to provide ad-blocking to my home network.

I was thinkering with Unbound to add a fully independent DNS resolver and not depend on Google/Adblock/Whatever upstream DNS server but i am unable to make Unbound work.

Top Level Domains (like com, org...) are resolved fine, but anything at second level doesn't. I am using "dig" (of course i am on linux) and Unbound logging to find out what's going on, but i am at a loss.

Could be my ISP blocking my requests? If i switch back to google DNS (for example) all works fine, but using my Unbound will only resolve TLDs and some random names. For example, it will resolve google.com but not kde.org...

Edit: somehow fixed by nuking config file and starting over.

top 9 comments
sorted by: hot top controversial new old
[–] mhzawadi@lemmy.horwood.cloud 4 points 4 months ago (1 children)

this might be what your looking for -> https://docs.pi-hole.net/guides/dns/unbound/

[–] Shimitar@feddit.it 1 points 4 months ago (2 children)

I have followed this guide, but still no way. "it" is resolved, but "polito.it" does not resolve, for example.

[–] Oisteink@feddit.nl 1 points 4 months ago

what does your trace give? You are setting up a recursive resolver, make sure settings allow for this

[–] mhzawadi@lemmy.horwood.cloud 1 points 4 months ago (1 children)

not sure your example domain is the best, can you lookup hrowood.biz?

[–] Shimitar@feddit.it 1 points 2 months ago

Old thread, but I have somehow solved by reinstalling unbound and nuking the old config file...

[–] Atherel@lemmy.dbzer0.com 3 points 4 months ago

Assuming you are logged in to the server running unbound, are the ns for .it reachable? Do all .com domains work and no .org?

Can you run dig +trace on a domain that doesn't work

[–] lemmyvore@feddit.nl 1 points 4 months ago (1 children)

What do the Unbound logs say?

What upstream servers are you using?

not depend on Google/Adblock/Whatever upstream DNS server

I mean, you're gonna have to get your DNS information somewhere. You can choose and pick your upstream but you still need one. You can cache the DNS info but you will still need to refresh it eventually. You can use a DoT or DoH upstream server so your ISP cannot spy on your DNS traffic but, again, you still need an upstream.

[–] Shimitar@feddit.it 1 points 4 months ago (1 children)

I want to go directly to the source, i mean, if i want to resolve, for example www.polito.it, i want to ask "it", then "polito.it"... This is what Unbound should be doing.

Instead, i can resolve it:

server /etc # dig it @127.0.0.1

; <<>> DiG 9.16.48 <<>> it @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59860
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;it.                            IN      A

;; AUTHORITY SECTION:
it.                     3194    IN      SOA     dns.nic.it. hostmaster.nic.it. 2024062114 10800 900 604800 3600

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Jun 21 14:50:06 CEST 2024
;; MSG SIZE  rcvd: 86

Instead i cannot resolve polito.it:

server /etc # dig polito.it @127.0.0.1

; <<>> DiG 9.16.48 <<>> polito.it @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 60832
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;polito.it.                     IN      A

;; Query time: 1180 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Jun 21 14:50:40 CEST 2024
;; MSG SIZE  rcvd: 38

Nothing appears in the logs. It resolve fine using 8.8.8.8 as upstream DNS.

[–] lemmyvore@feddit.nl 2 points 4 months ago* (last edited 4 months ago)

polito.it may not be the best example because its A records point at private IPs (192.168.x.x). Such records are often filtered by ISP DNS servers because they are used in certain kinds of attacks.

Double check your results using DNSChecker.

Edit: also, using just dig will not resolve all possible records related to a domain. I use a script that asks dig explicitly for a variety of record types:

#!/bin/bash
echo "SOA NS A AAAA MX CNAME TXT SRV DNSKEY"|\
xargs -n1 dig +noall +answer +nocrypto "$@"|\
sort -u -k4