Post 9kaAFJVhKCIskZbu1Q by neon@moe.neon.moe
(DIR) More posts by neon@moe.neon.moe
(DIR) Post #9ka6sa9F041ZpQZjrE by neon@moe.neon.moe
2019-07-06T18:35:45Z
0 likes, 0 repeats
One of my servers can't reach git.neon.moe, even though the rest of the internet can, :angryfelix:
(DIR) Post #9ka7lOaLgwjxtVOMs4 by Wolf480pl@niu.moe
2019-07-06T18:45:41Z
0 likes, 0 repeats
@neon what does mtr say?
(DIR) Post #9ka7v5OlslaDHdb6lU by neon@moe.neon.moe
2019-07-06T18:47:26Z
0 likes, 0 repeats
@Wolf480pl Haven't used it before so I'm not sure I got the syntax right, but `mtr git.neon.moe` just says:Failed to resolve host: git.neon.moe: Name or service not known
(DIR) Post #9ka8ZQXQhlYkQjspzE by Wolf480pl@niu.moe
2019-07-06T18:54:44Z
0 likes, 0 repeats
@neon it's supposed to be like traceroute but animated...Anyway, looks like something's wrong with DNS...you can1. try to get the IP of git.neon.moe (eg. by doing ping git.neon.moe on another computer) and see if that IP is reachable from your server.2. Try `dig git.neon.moe` and see what response you get (in particular, the status, and the SOA record, if any), 3. also try `dig git.neon.moe @8.8.8.8` to ask google DNS servers instead of your default DNS servers and see if there's any difference.
(DIR) Post #9ka92GUl7jozgENx3o by neon@moe.neon.moe
2019-07-06T18:59:56Z
0 likes, 0 repeats
@Wolf480pl Pinging the IP works, dig works (status is NOERROR), but ping does not. And I originally noticed this because caddy couldn't connect to my git server, so it's not just ping either. Any ideas?
(DIR) Post #9ka96A6goiMP1ez98q by Wolf480pl@niu.moe
2019-07-06T19:00:41Z
0 likes, 0 repeats
@neon does dig return an A record, or no records at all?
(DIR) Post #9ka98JCzwpQtpjxYwK by neon@moe.neon.moe
2019-07-06T19:01:01Z
0 likes, 0 repeats
@Wolf480pl It returns an A record, and it is the correct one.
(DIR) Post #9ka9JOBfmHZmSZchkm by Wolf480pl@niu.moe
2019-07-06T19:03:03Z
0 likes, 0 repeats
@neon hmm... ok and what happens if you run`getent hosts git.neon.moe` ?
(DIR) Post #9ka9VrxEvhvcFwp6iO by neon@moe.neon.moe
2019-07-06T19:05:18Z
0 likes, 0 repeats
@Wolf480pl It just prints nothing.
(DIR) Post #9ka9a5UwW6y9Q3bCz2 by Wolf480pl@niu.moe
2019-07-06T19:06:03Z
0 likes, 0 repeats
@neon sounds like you have something wrong with your /etc/nsswitch.conf... but do other domains work?Also, do you by chance have nscd running?
(DIR) Post #9ka9txPuGwyQ9CiaB6 by neon@moe.neon.moe
2019-07-06T19:09:38Z
0 likes, 0 repeats
@Wolf480pl Pinging google.com does work. I wonder what could be wrong with that config, I don't think I've ever touched it. And I don't think so, at least ps -A | grep nscd didn't return anything.Is there like a good config I should compare the /etc/nsswitch.conf to or?
(DIR) Post #9kaA41KUa1PdB6z4N6 by Wolf480pl@niu.moe
2019-07-06T19:11:29Z
0 likes, 0 repeats
@neon well, take a look at the hosts line. Mine is:hosts: files dns
(DIR) Post #9kaAFJVhKCIskZbu1Q by neon@moe.neon.moe
2019-07-06T19:13:30Z
0 likes, 0 repeats
@Wolf480pl Oh, mine was `hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns`, now this all makes some sort of sense :happyfelix: Removing the unavail-bit worked like a charm, thank you very much for the help 🙇
(DIR) Post #9kaAiTLFqmERdkd5l2 by Wolf480pl@niu.moe
2019-07-06T19:18:47Z
0 likes, 0 repeats
@neon >resolve>systemd-resolvedsigh...I recommend disabling systemd-resolved somehow, but I don't remember how to do this correctly.I've heard of a lot of people having problems with it, and AFAIK there isn't much of a reason to use it.