• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Just finished installation: Unable to ping domain names?

T

tkambler

Guest
I have just finished installing Plesk 8.0.1 for Ubuntu 5.10. Installation went perfectly.

I am now at the shell, and attempting to run the following command:

ping yahoo.com

The machine is unable to resolve the host. I am able, however, to ping IP addresses:

ping 216.109.112.135

Can anyone tell me how to resolve this? Would this be due to an improper bind setup?

I have no desire to run bind on this machine, anyways. All DNS will be handled off-site.

Thanks!
 
You might want to check /etc/resolv.conf to make sure there is something in there.

search (a domain on this server)
nameserver (the ip of your ns1)
nameserver (the ip of your ns2)

You can also use the ip's of your DC's nameservers if they have them.
 
Originally posted by tkambler
I have just finished installing Plesk 8.0.1 for Ubuntu 5.10. Installation went perfectly.

I am now at the shell, and attempting to run the following command:

ping yahoo.com

The machine is unable to resolve the host. I am able, however, to ping IP addresses:

ping 216.109.112.135

Can anyone tell me how to resolve this? Would this be due to an improper bind setup?

I have no desire to run bind on this machine, anyways. All DNS will be handled off-site.

Thanks!
Click to expand...

Wow, I feel like an idiot. It's always the simplest thing. I could've sworn I set that, but looks like I failed to do so this time. Thanks. :)
 
You must log in or register to reply here.

Similar threads

nethubonline
Forwarded to devs plesk repair mail fails with "Unable to find row with id 0 in dns_zone table" when DKIM is enabled and no DNS server is installed
Replies
1
Views
1K
Sebahat.hadzhi
Sebahat.hadzhi
N
Issue Enabling DNSSec for existing keys -- Workaround for double plesk bug.
Replies
3
Views
525
SirAdams
SirAdams
first4it
Issue Docker containers unable to resolve DNS or access external network on Plesk Obsidian 18.0.76 Update #4 (Collabora / Nextcloud issue)
Replies
2
Views
5K
first4it
first4it
J
Resolved Atomic Advanced ~ Unable to get Rulesets
Replies
4
Views
4K
JeffreyReed
J
TheColin21
Resolved Docker outbound traffic gets blocked after 18.0.67 Update #3
2
Replies
28
Views
29K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top