> I registered news.coin domain and set the IP 192.227.235.xx, and at the day before yesterday,
> I use name_update to reset the IP to 138.128.120.111, the problem was happened!
The problem in your local caches, where saved old IP.
With EMCDNS, your address resolved correctly:
$ dig
news.coin @localhost -p5335
; <<>> DiG 9.8.3-P4 <<>> news.coin @localhost -p5335
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51597
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;news.coin. IN A
;; ANSWER SECTION:
news.coin. 86400 IN A 138.128.120.111Also, same work for emergate:
$ host news.coin.emergate.net
news.coin.emergate.net has address 138.128.120.111
Thus, you see, DNS system works OK.
I think, you did not specified TTL value for your record.
And, as written in the document:
http://emercoin.com/DNS_and_Name-Value_Storage The default value for TTL is 24 hours.
So, I assume, everything works, but old record exist in some your cache.
When it will be expired, a new value will be loaded.
> Please fix this problem DEV.
We cannot refresh caches on _your_ computers, sorry.
Just wait, please.