• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

after chaging ip domains not reachable

M

MeinN

Guest
After I have changed IP in Virtuozzo and Plesk (Domains changed IP with "Setup") the domains are not rechable. what can i do to fix the problem. ping command is successful. I had to install plesk 8.6 because 9.2 was a disaster with his cpu problem and the graylists.
 
Hello,

Please make sure that your domain is resolved by your DNS servers correctly. You can do this by using the following command (example):

===

[akucherov@support akucherov]$ dig google.com a

; <<>> DiG 9.2.4 <<>> google.com a
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49229
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;google.com. IN A

;; ANSWER SECTION:
google.com. 300 IN A 74.125.45.100
google.com. 300 IN A 74.125.67.100
google.com. 300 IN A 74.125.127.100

;; AUTHORITY SECTION:
google.com. 53536 IN NS ns3.google.com.
google.com. 53536 IN NS ns4.google.com.
google.com. 53536 IN NS ns1.google.com.
google.com. 53536 IN NS ns2.google.com.

;; ADDITIONAL SECTION:
ns1.google.com. 308263 IN A 216.239.32.10
ns2.google.com. 308263 IN A 216.239.34.10
ns3.google.com. 308263 IN A 216.239.36.10
ns4.google.com. 308263 IN A 216.239.38.10

;; Query time: 20 msec
;; SERVER: 64.131.90.25#53(64.131.90.25)
;; WHEN: Sun Sep 13 05:20:57 2009
;; MSG SIZE rcvd: 212

===
 
Back
Top