nsXX.zoneedit.com not updating

Ben M

New Member
I'm updating a dynamic IP via a Tomato router, using a DYN authentication token. The cp.zoneedit.com DNS Settings page shows the updated IP address. However I get very inconsistent results from zoneedit's nameservers (see below). For reference, I am supposed to use ns12 and ns15. The correct address is 50.137.137.132, while 73.25.27.41 is the old address.

Any idea what's going on? Thanks!

user@host ~ $ nslookup tensorial.com ns12.zoneedit.com
Server: ns12.zoneedit.com
Address: 46.101.18.226#53

Name: tensorial.com
Address: 50.137.137.132

user@host ~ $ nslookup tensorial.com ns15.zoneedit.com
Server: ns15.zoneedit.com
Address: 166.88.18.61#53

Name: tensorial.com
Address: 73.25.27.41

user@host ~ $ nslookup tensorial.com dns1.zoneedit.com
Server: dns1.zoneedit.com
Address: 162.220.33.236#53

Name: tensorial.com
Address: 73.25.27.41

user@host ~ $ nslookup tensorial.com dns2.zoneedit.com
Server: dns2.zoneedit.com
Address: 166.88.18.58#53

Name: tensorial.com
Address: 73.25.27.41

user@host ~ $ nslookup tensorial.com dns2.zoneedit.com
Server: dns2.zoneedit.com
Address: 166.88.18.58#53

Name: tensorial.com
Address: 73.25.27.41
 

sandy

Administrator
Staff member
Hi there

only ns12 and ns15 would be of concern as they are the servers delegated. For your dynamic records.. i see they all have the same IP... may I suggest that you modify the dyn records to be one for the root domain and another for a wildcard using the * as the host... and to set the TTLs no shorter then 600 seconds... and let me know how that works going forward.

thanks
sandy
 

sandy

Administrator
Staff member
oh... i reloaded the zone manually and now it looks good:

dig @ns15.zoneedit.com a tensorial.com

; <<>> DiG 9.8.3-P1 <<>> @ns15.zoneedit.com a tensorial.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45291
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

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

;; ANSWER SECTION:
tensorial.com. 300 IN A 50.137.137.132

dig @ns12.zoneedit.com a tensorial.com

; <<>> DiG 9.8.3-P1 <<>> @ns12.zoneedit.com a tensorial.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59344
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

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

;; ANSWER SECTION:
tensorial.com. 300 IN A 50.137.137.132
 

Ben M

New Member
Thanks for the advice! As recommended, I changed TTL to 600 and switched over to just *,@ for hostnames. Any idea why the nameservers didn't update? Was TTL 300 breaking something? I feel like I've experienced similar glitches in the past.
 

sandy

Administrator
Staff member
sometimes... with DYN updates for multiple hosts.. if they come in too rapid a succession... we may receive one while the zone is reloading.. when that happens the dyn record we received while reloading may not make it on to the actual zone file

sandy
 

Ben M

New Member
Hi there! Two weeks ago my IP changed, and even though I have long since implemented your suggestions, the exact same issue recurred. Namely, the correct IP (67.170.184.132) appears on the cp.zoneedit.com DNS Settings page. However, all the nameservers listed unanimously give the old IP (50.137.137.132).

I'm going to try to force an update right now, but I wanted to announce that there seems to be some sort of bug.

dig @ns15.zoneedit.com a tensorial.com

; <<>> DiG 9.10.3-P4-Ubuntu <<>> @ns15.zoneedit.com a tensorial.com
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28198
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;tensorial.com. IN A

;; ANSWER SECTION:
tensorial.com. 600 IN A 50.137.137.132

;; Query time: 310 msec
;; SERVER: 166.88.18.61#53(166.88.18.61)
;; WHEN: Thu Jul 13 22:52:47 BST 2017
;; MSG SIZE rcvd: 58
 

sandy

Administrator
Staff member
Hi there

please make sire the the DYN records TTL is no less then 600 seconds I have changed this now.
there may be something on your DDNS client that is sending a 0second ttl for these records...

in addition at the domains registrar and in the NS records on the zoneedit zone file please remove the current ns12 and ns5 and replace them with:
dns1.zoneedit.com
dns2.zoneedit.com

thanks
sandy
 
Top