Selfhosted

39253 readers

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

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

It's always DNS, should I complain? (self.selfhosted)

submitted 1 year ago* (last edited 1 year ago) by aesir to c/selfhosted

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

[–] [email protected] 2 points 1 year ago (1 children)

I would probably send along the output of dig your.domain @uni-ip and dig your.domain @8.8.8.8 and dig your.domain @1.1.1.1 and dig your.domain @your-domains-authoritative-dns-server if you have that or some similar DNS client tool installed that allows direct requests to specific servers. If you don't know the authoritative DNS servers for your domain, those are the ones in the NS records.

[–] aesir 2 points 1 year ago (1 children)

Nice, I am routed to sinkhole.paloaltonetworks.com I am a malicious domain apparently.

[–] MaxVerstappen 1 points 1 year ago

Are you hosting a service that is not under your organizations official domain or something? It is common security practice to block newly created domains which may be why your domain is blacklisted if you only recently stood it up.