We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
I had changed the NS server of my domain but dig command still shows old NS server
-
- Posts: 301
- Joined: Tue Dec 22, 2015 2:06 pm
I had changed the NS server of my domain but dig command still shows old NS server
Today I tried to change the NS server of my domain. This should be a very simple thing but the result is not.
At first, I edited the "NS Server" option on the domain management page of my domain name registration provider:
from the old ones:
f1g1ns1.dnspod.net
f1g1ns2.dnspod.net
to new ones:
cody.ns.cloudflare.com
kay.ns.cloudflare.com
After about 10 minutes, I saw following message on Cloudflare website:
Why my vestacp server did not update the NS Records (or cache?) according to my new NS Server ?
How to solve this problem?
Thank you.
At first, I edited the "NS Server" option on the domain management page of my domain name registration provider:
from the old ones:
f1g1ns1.dnspod.net
f1g1ns2.dnspod.net
to new ones:
cody.ns.cloudflare.com
kay.ns.cloudflare.com
After about 10 minutes, I saw following message on Cloudflare website:
But, when I now run the following command on my VestaCP server via the SSH terminal, I saw different NS Server :This website is active on Cloudflare.
Code: Select all
# dig joomlagate.com
; <<>> DiG 9.9.4-RedHat-9.9.4-51.el7_4.2 <<>> joomlagate.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33790
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 11
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;joomlagate.com. IN A
;; ANSWER SECTION:
joomlagate.com. 600 IN A 120.27.137.71
;; AUTHORITY SECTION:
joomlagate.com. 61977 IN NS f1g1ns1.dnspod.net.
joomlagate.com. 61977 IN NS f1g1ns2.dnspod.net.
;; ADDITIONAL SECTION:
f1g1ns1.dnspod.net. 130022 IN A 182.140.167.166
f1g1ns1.dnspod.net. 130022 IN A 14.215.150.17
f1g1ns1.dnspod.net. 130022 IN A 58.247.212.36
f1g1ns1.dnspod.net. 130022 IN A 61.151.180.44
f1g1ns1.dnspod.net. 130022 IN A 180.163.19.15
f1g1ns2.dnspod.net. 129662 IN A 182.140.167.188
f1g1ns2.dnspod.net. 129662 IN A 52.220.136.67
f1g1ns2.dnspod.net. 129662 IN A 61.129.8.159
f1g1ns2.dnspod.net. 129662 IN A 101.226.220.16
f1g1ns2.dnspod.net. 129662 IN A 121.51.128.164
;; Query time: 9 msec
;; SERVER: 10.143.22.118#53(10.143.22.118)
;; WHEN: Wed Mar 14 14:56:09 CST 2018
;; MSG SIZE rcvd: 273
How to solve this problem?
Thank you.