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.
 

Eotnak

New Member
Well I thought I fixed it by having NS records created on the Web host (authoritative for fluidphysio.com) it was what they told me that I needed to do. The NS records for vpn.fluidphysio.com point to ns8.zoneedit.com and ns12.zoneedit.com. Is this the right way to do this? Right now there is no IP being resolved for vpn.fluidphysio.com.

Thanks again for the help.
 

Chris Cherry

Mr. Happy To Help You.
Hello,

Since you're not delegating the root zone to Zoneedit, then there is no need to have the root zone in our system. What needed to be set up on our end is a specific zone for "vpn.fluidphysio.com" - which I've set up in your account.

Next, what you'll want to do is go into that zone and set up the DNS.

Do not add a hostname of "vpn" to the record or it becomes vpn.vpn.fluidphysio.com.

If you were to add a DYN Record for this zone, use "@" as the Host and then the IP address. That will set up "vpn.fluidphysio.com" which will resolve to the IP address you prefer.
 

Eotnak

New Member
Thank you again for all of your help, Chris. I'm getting a great lesson in the inner inner workings of DNS here.

I added the DYN record with @ and IP, but still no resolution going on. I ran some free DNS tools but can't make any sense of what to do with the errors.

-Tom
 

Chris Cherry

Mr. Happy To Help You.
Can you change the NS Record setup in the DNS zone with server268.com?

To the following:
vpn.fluidphysio.com IN NS dns1.zoneedit.com
vpn.fluidphysio.com IN NS dns2.zoneedit.com


At the moment, I see them delegated to the old ones that were on the root zone when that was set up here:

vpn.fluidphysio.com. 2560 IN SOA ns12.zoneedit.com. hostmaster.vpn.fluidphysio.com. 1580806871 16384 2048 1048576 2560
vpn.fluidphysio.com. 14400 IN NS ns12.zoneedit.com.
vpn.fluidphysio.com. 14400 IN NS ns8.zoneedit.com.
;; Received 130 bytes from 192.252.145.18#53(ns2.server268.com) in 22 ms

Give that time to propagate and I'll check in on this in the morning.
 

Eotnak

New Member
Hi Chris. Changes have been made with the Web host. Hopefully things look better on your end, but I'm still not resolving here.
 

Chris Cherry

Mr. Happy To Help You.
I'm encountering the same issue. However, if you submit a query directly to our DNS, they do report back with the proper IP. We're checking things out here to see if we can find the cause.

 

Chris Cherry

Mr. Happy To Help You.
Everything checks our here which leads us to believe that something isn't set up correctly in the DNS zone within your root domain.

Can you confirm that you've set up "NS Records" on the sub-domain "vpn" in the zone for fluidphysio.com with your current DNS host?. You don't have "vpn.fluidphysio.com" set up as some other record type?

When I do a "dig +trace vpn.fluidphysio.com a"

The end result is the server ns2.server268.com reporting back the information below:

vpn.fluidphysio.com. 2560 IN SOA dns1.zoneedit.com. hostmaster.vpn.fluidphysio.com. 1580964806 16384 2048 1048576 2560
;; Received 98 bytes from 192.252.145.18#53(ns2.server268.com) in 21 ms


The serial number reported above is the same serial number for your root:

dig @ns1.server268.com fluidphysio.com soa
fluidphysio.com. 2560 IN SOA ns1.server268.com. hostmaster.fluidphysio.com. 1580964806 16384 2048 1048576 2560


On our system:

dig @dns1.zoneedit.com vpn.fluidphysio.com soa
vpn.fluidphysio.com. 300 IN SOA dns0.zoneedit.com. zone.zoneedit.com. 1580997669 3600 600 1209600 300


So, something doesn't seem to be working as it should?
 
Top