Changed DYN DNS subdomain, new IP not propagating

Eotnak

New Member
Hi, I searched the knowledge base and got nowhere, contacted support and got no response. I've never had this problem before. When I try to resolve vpn.fluidphysio.com, I get the old IP address 73.160.239.16. I updated it through the Web interface several days ago and still not propagating.

Original TTL was 60 seconds. 24 hours after the change, I thought ISP's were overriding my TTL so I changed it to 1800 seconds. Still nothing.
Usually the change gets propagated in a few minutes. Any ideas? Thank you.
 

Chris Cherry

Mr. Happy To Help You.
Hello there,


The domain name you mentioned is not using Zoneedit for DNS. Any changes you make in our portal is not seen by the internet.

Domain Name: FLUIDPHYSIO.COM
Registry Domain ID: 1994817260_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2019-04-24T04:16:41Z
Creation Date: 2016-01-16T16:12:59Z
Registry Expiry Date: 2021-01-16T16:12:59Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.SERVER268.COM
Name Server: NS2.SERVER268.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2020-01-14T17:24:30Z <<<


dig +trace vpn.fluidphysio.com a

; <<>> DiG 9.10.3-P4-Debian <<>> +trace vpn.fluidphysio.com a
;; global options: +cmd
. 1428 IN NS m.root-servers.net.
. 1428 IN NS a.root-servers.net.
. 1428 IN NS f.root-servers.net.
. 1428 IN NS e.root-servers.net.
. 1428 IN NS i.root-servers.net.
. 1428 IN NS b.root-servers.net.
. 1428 IN NS j.root-servers.net.
. 1428 IN NS c.root-servers.net.
. 1428 IN NS h.root-servers.net.
. 1428 IN NS k.root-servers.net.
. 1428 IN NS d.root-servers.net.
. 1428 IN NS l.root-servers.net.
. 1428 IN NS g.root-servers.net.
;; Received 525 bytes from 64.68.199.53#53(64.68.199.53) in 7 ms

com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 1179 bytes from 192.203.230.10#53(e.root-servers.net) in 2 ms

fluidphysio.com. 172800 IN NS ns1.server268.com.
fluidphysio.com. 172800 IN NS ns2.server268.com.
;; Received 675 bytes from 192.33.14.30#53(b.gtld-servers.net) in 24 ms

vpn.fluidphysio.com. 14400 IN A 73.160.239.16
fluidphysio.com. 25920 IN NS ns1.server268.com.
fluidphysio.com. 25920 IN NS ns2.server268.com.
;; Received 131 bytes from 192.252.145.18#53(ns2.server268.com) in 21 ms
 

Eotnak

New Member
Oh wow, it's always the simple problems that get me...no wonder I couldn't find the answer.
Thank you Chris.
 
Top