Selfhosted

40041 readers

680 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

It's always DNS, should I complain? (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by aesir@lemmy.world to c/selfhosted@lemmy.world

5 comments fedilink hide all child comments

Hi,

What to do if the domain name of one of my webserver, that me and some lab members use for work related stuff, is no longer resolved by our university DNS? When I first noticed it, I could see no resolution at all while now the domain resolves to a wrong IP. The site can be normally reached on any other network so there is no problem on my side I think.

Should I just wait (now more than 24 hours) or should I try anything? I am entitled to complain to our IT even though the issue is only with this not-really-professional FreeDNS subdomain?

EDIT: apparently some automatism marked this domain as malicious (absolutely it is not, not willingly and not compromised) and somehow DNS resolves to CNAME sinkhole.paloaltonetworks.com.

top 5 comments

sorted by: hot top controversial new old

[–] ChrislyBear@lemmy.world 1 points 1 year ago (1 children)

Why are you using a crappy uni DNS? Why not 1.1.1.1 or OpenDNS or even Google's 8.8.8.8?

[–] aesir@lemmy.world 0 points 1 year ago (1 children)

Well, the main point is I would need to manually change this for tens of pcs and its not my job, moreover other people should to the same on theirs. Nevertheless, I just tried 8.8.8.8 on a couple of PCs and I have the same issue! It appears that my DNS setting is irrelevant as it is overwritten down the chain, the only way I can reach the site is put the line in etc/hosts. Could it be?

[–] ChrislyBear@lemmy.world 0 points 1 year ago (1 children)

Yes, your uni might intercept communication on port 53 and reroute it to their DNS servers. It's possible.

[–] original_ish_name@latte.isnot.coffee 1 points 1 year ago

In that case just use a DNS that listens on a different port

[–] dartanjinn@lemm.ee -1 points 1 year ago

Cloudflare tunnel is the easy solution here. It'll cost you a couple bucks a year for a domain name but you'll have no more DNS issues.