Can not resolve hostname что делать
Minecraft – Can’t Resolve Hostname Error Fix
Home / Minecraft / Minecraft – Can’t Resolve Hostname Error Fix
It’s very popular for modern Minecraft servers to use a “hostname” instead of a traditional IP address. A hostname acts similar to a domain name, but one that is used to connect to the server. Typically servers will add the “play” subdomain to achieve this.
The “can’t resolve hostname” error in Minecraft means that the game is unable to find the hostname that you are entering.
Fixing “Can’t Resolve Hostname”
There are a number of different reasons this error can occur. Some are more simple than others. It can range from mistyping the name, to issues with a firewall or router settings.
Firstly, make sure that you are typing the correct name! Any extra characters or symbols or spaces will prompt this error. It must be exact.
If this doesn’t work, the next step is to try connecting to the actual IP address of the server. Many times servers that use hostnames will not display their IP address as well. We can find it though!
This address that we’ve copied is the actual IP of the server! We can now enter this IP directly into Minecraft to connect.
Still not working?
If entering the direct IP address does not work, there may be an error with the server. There is a quick way we can test our connection to the server without using Minecraft.
This will display your connection to the server. If you receive “Request timed out.” at any point during this process, it means that you are not able to establish a connection to the server. For the most part, this means it is offline.
If the pinging process completed without this error, it usually means there is an underlying issue with a firewall. This can be occurring from your side, or on the end of the server. It is best to contact the server administrators if you cannot connect at this point
Troubleshooting: Can’t Resolve Hostname
You may find the “can’t resolve hostname” or “temporary failure in name resolution” error when using retrieval command like wget, cURL, ping or nslookup. There are many reasons why these commands can cause an error, including file corruption.  For the sake of brevity, we look towards commonalities between these commands to solve the issue.
These commands connect to the Internet using gateways to communicate and provide information.   If the connection from your local machine, in this case, a CentOS server, is disconnected you’ll likely run into issues trying to access the world wide web. In this troubleshooting tutorial, we’ll show you some common solutions to connectivity issues.
Step 1: Amongst many other configuration tasks, the resolv.conf file is used to resolve DNS requests. Manually editing the resolv.conf file to configure name resolution will only do so temporarily. The Network Manager controls this essential /etc/resolv.conf file to create permanent changes. So, we’ll first stop and disable the Network Manager:
chkconfig NetworkManager off; service NetworkManager stop
Step 2: The method for permanent changes is to edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file instead of resolv.conf file. Open the file:
Next, we’ll set our DNS IP’s to use Google’s Public DNS (8.8.8.8 & 8.8.4.4).
DEVICE=»em1″
BOOTPROTO=»static»
DNS1=»127.0.0.1″
DNS2=»8.8.8.8″
DNS3=»8.8.4.4″
GATEWAY=»some_ip»
HWADDR=»hwid»
IPADDR=»some_ip»
IPV6INIT=»yes»
NETMASK=»255.255.255.0″
NM_CONTROLLED=»yes»
ONBOOT=»yes»
TYPE=»Ethernet»
Save and quit the file using ESC and :wq.
Step 3: Enable and restart your network, using the commands associated with your server version.
CentOS 6, CloudLinux 6, RHEL 6:
chkconfig network on
service network start
CentOS 7, CloudLinux 7, RHEL 7:
systemctl enable network.service
systemctl start network.service
Step 4: T est the reachability of a host by using ping, curl, wget or any testing tool of your choice. In our example, we’ve successfully ping’d Google! В
ping google.com
PING google.com (172.217.4.46) 56(84) bytes of data.
64 bytes from lga15s46-in-f14.1e100.net (172.217.4.46): icmp_seq=1 ttl=57 time=6.65 ms
64 bytes from lga15s46-in-f14.1e100.net (172.217.4.46): icmp_seq=2 ttl=57 time=6.68 ms
64 bytes from lga15s46-in-f14.1e100.net (172.217.4.46): icmp_seq=3 ttl=57 time=6.68 ms
You don’t have to rack your brain over connectivity issues!В Liquid Web customers enjoy 24/7 support for our VPS Managed products. Our knowledgeable team of support techs have experience with solving errors of this nature.В Access our support team through a ticket, chat or phone call!
ssh: Could not resolve hostname [hostname]: nodename nor servname provided, or not known [closed]
Want to improve this question? Update the question so it’s on-topic for Stack Overflow.
However, I can log into the server with,
The server is a Raspberry Pi Model B running the latest distribution of Raspbian and the machine I am trying to connect to it with is a Macbook Pro running Mavericks. ssh was enabled on the Raspberry Pi when I set up Raspbian.
I have perused Stack Overflow for hours trying to see if anyone else had this problem and I have not found anything. Every ssh tutorial I find says that I should just be able to set it up on the remote machine and log in from anywhere using a hostname, and I have never had success with that.
16 Answers 16
If you’re on Mac, restarting the DNS responder fixed the issue for me.
I had the same issue connecting to a remote machine. but I managed to login as below:
Recently I came across the same issue. I was able to ssh to my pi on my network, but not from outside my home network.
Also, I set up port forward on my router for hosting a web site and I had even port forward port 22 to my pi’s static IP for ssh, but I left the field blank where you specify the application you are performing the port forwarding for on the router. Anyway, I added ‘ssh’ into this field and, VOILA! A working ssh connection from anywhere to my pi.
I’ll write out my router’s port forwarding settings.
(ApplicationTextField)_ssh (external port)_22 (Internal Port)_22 (Protocal)_Both (To IP Address)_192.168.1.### (Enabled)_checkBox
Port forwarding settings can be different for different routers though, so look up directions for your router.
Now, when I am outside of my home network I connect to my pi by typing:
Then I am able to input my password and connect.
Can not resolve host name
После запуска 12 сервера перестал обновляться клиент.
сделал ipconfig /flushdns
и добавил в файл «hosts»:
95.129.248.90 launcher.l2.ru
109.105.130.68 patch.l2.ru
95.129.248.195 gameguard.l2.ru
95.129.248.196 auth.l2.ru
клиент обновился, но при вводе логина и пароля возникает ошибка: Can not resolve host name.
Пробовал в hosts ставить 127.0.0.1, клиент снова не обновляется.
Так же не открывается в браузере форум 4гейм, ЦУП.
Можно ли что нибудь сделать?
ipconfig /displaydns что выдает?
В реестре проверить можно ключ «HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\servi c es\Tcpip\Parameters\DataBasePath».
Какого типа параметр? Дословно сюда.
Плюс, правильный ли путь?
Добавлено через 2 минуты
Я епта даже не пойму в чем дело. Из-за чего эта проблема.
Иннова? Провайдер? Или у меня что-то? У меня все норм работало, вот уже скок времени, и я ничего не менял в компе. D:
Аналогично после запуска 12-го серва не обновлялось и Can not resolve hostname. Щас обновляется но всё равно Can not resolve hostname
Угнова мать её
Добавлено через 4 минуты
во все заработало 🙂 наконецто
вот что прописывал
95.129.248.90 launcher.l2.ru
109.105.130.68 patch.l2.ru
95.129.248.195 gameguard.l2.ru
95.129.248.196 auth.l2.ru
109.105.130.129 geo.l2.ru
Добавлено через 11 минут
всё, заработало,
именно с этими строчками
ssh: Could not resolve hostname [hostname]: nodename nor servname provided, or not known [closed]
Want to improve this question? Update the question so it’s on-topic for Stack Overflow.
However, I can log into the server with,
The server is a Raspberry Pi Model B running the latest distribution of Raspbian and the machine I am trying to connect to it with is a Macbook Pro running Mavericks. ssh was enabled on the Raspberry Pi when I set up Raspbian.
I have perused Stack Overflow for hours trying to see if anyone else had this problem and I have not found anything. Every ssh tutorial I find says that I should just be able to set it up on the remote machine and log in from anywhere using a hostname, and I have never had success with that.
16 Answers 16
If you’re on Mac, restarting the DNS responder fixed the issue for me.
I had the same issue connecting to a remote machine. but I managed to login as below:
Recently I came across the same issue. I was able to ssh to my pi on my network, but not from outside my home network.
Also, I set up port forward on my router for hosting a web site and I had even port forward port 22 to my pi’s static IP for ssh, but I left the field blank where you specify the application you are performing the port forwarding for on the router. Anyway, I added ‘ssh’ into this field and, VOILA! A working ssh connection from anywhere to my pi.
I’ll write out my router’s port forwarding settings.
(ApplicationTextField)_ssh (external port)_22 (Internal Port)_22 (Protocal)_Both (To IP Address)_192.168.1.### (Enabled)_checkBox
Port forwarding settings can be different for different routers though, so look up directions for your router.
Now, when I am outside of my home network I connect to my pi by typing:
Then I am able to input my password and connect.