DNS issues since recently
by Ramurd from LinuxQuestions.org on (#6NPXS)
Recently I switched to Slackware current, so the culprit may lie in that direction; but maybe there are some people here that may give me an indication what may be off here. (I'm a pretty old-fashioned Linux user for quite a few years now and this one has me stumped)
The issue: some curl requests and sbocheck fail to resolve hostnames.
However, when I do nslookup I do get the hostnames resolved. In this particular case: in those cases sbocheck will resolf (but fail because the directory is not empty, removing it and running the command again usually succeeds, an update shortly thereafter tends to fail)
Same for my kid, who wanted to play minecraft. I installed it for him and we tried to login to his account. However, hostname lookups fail.
One of the links I took, snipped (because I'm lazy) it a bit and performed it in curl:
Code:curl -L -v -v -v https://launchermeta.mojang.com/v1/products/launcherIt fails: curl: (6) Could not resolve host: launchermeta.mojang.com
Then: Code:nslookup launchermeta.mojang.com provides a hostname immediately
Rerunning curl (the resolved host should now be in cache) still fails.
Strangely: dig gives a timeout on port 53
What do dig and curl do different than nslookup and how do I work around this?
Could it be IPv6? Some weird setting on my router?
The issue: some curl requests and sbocheck fail to resolve hostnames.
However, when I do nslookup I do get the hostnames resolved. In this particular case: in those cases sbocheck will resolf (but fail because the directory is not empty, removing it and running the command again usually succeeds, an update shortly thereafter tends to fail)
Same for my kid, who wanted to play minecraft. I installed it for him and we tried to login to his account. However, hostname lookups fail.
One of the links I took, snipped (because I'm lazy) it a bit and performed it in curl:
Code:curl -L -v -v -v https://launchermeta.mojang.com/v1/products/launcherIt fails: curl: (6) Could not resolve host: launchermeta.mojang.com
Then: Code:nslookup launchermeta.mojang.com provides a hostname immediately
Rerunning curl (the resolved host should now be in cache) still fails.
Strangely: dig gives a timeout on port 53
What do dig and curl do different than nslookup and how do I work around this?
Could it be IPv6? Some weird setting on my router?