this post was submitted on 20 Jul 2023
24 points (92.9% liked)

Selfhosted

40218 readers
948 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
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
24
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
32 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.

you are viewing a single comment's thread
view the rest of the comments
[–] ChrislyBear@lemmy.world 5 points 1 year ago (4 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 2 points 1 year ago (2 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 3 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 2 points 1 year ago

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

load more comments (1 replies)