Пользователи критикуют Discount Domains за задержки в обновлении DNS-записей

Does anyone know how often Discount Domains actually make DNS changes??? Doing something for a client who's domains are with DD (Groan). Their developer emailed me with an urgent request to change a CNAME record. I went on, changed it, looked at the TTL and saw it was set to an hour so was pretty hopeful it'd be a quick fix. Of course I totally forgot that making a DNS change online leads to an indeterminate ammount of time until the change is even loaded onto their own DNS servers. You read this help and they prattle on about TTL's and propergation etc and say allow up to 24 - 72 hours. The issue is I want to know when do they actually make the change on their own server??? Its as if since the change we enter changes on the website which generates an email to someone for them to make the changes. I can't get over quite how bad they still are - I figured some of it was the pain of transition of ownership and integration of platforms etc but no. They are still just as bad as ever. Was the previous TTL set to an hour? If it wasn't then DNS caches would keep the old record until the TTL for that has expired -- another possibility for why you're still seeing old records. You should also be able to use a DNS utility (e.g. dig) to query their DNS servers directly to see what record they're giving out for it right now. If not sure just look up the domain on dnc.org.nz (assuming it is a .nz) and it'll show the DNS servers at the bottom you can query. This would confirm your theory pretty quickly. Was the previous TTL set to an hour? If it wasn't then DNS caches would keep the old record until the TTL for that has expired -- another possibility for why you're still seeing old records. You should also be able to use a DNS utility (e.g. dig) to query their DNS servers directly to see what record they're giving out for it right now. If not sure just look up the domain on dnc.org.nz (assuming it is a .nz) and it'll show the DNS servers at the bottom you can query. This would confirm your theory pretty quickly. I'm fully aware of how TTL's work. I'm querying Discount Domains own servers directly using kloth.net and/or mxtoolbox.com. It took over an hour but I stopped checking regularly and its now changed. Kind of defeats the purpose of allowing low TTL's when it takes more than an hour for changes to go live on the authorative name servers. I went on, changed it, looked at the TTL and saw it was set to an hour so was pretty hopeful it'd be a quick fix. ever. mobiusnz: It took over an hour but I stopped checking regularly and its now changed. Seems to be working as designed. I'd recommend querying the DNS directly using dig or similar commands so you are querying their DNS servers directly. Easy to do from the command line. MxToolbox etc may do their own caching so I wouldn't rely on them. I'd recommend querying the DNS directly using dig or similar commands so you are querying their DNS servers directly. Easy to do from the command line. MxToolbox etc may do their own caching so I wouldn't rely on them. AGAIN - I use MXToolbox often who lookup who the root authorative DNS server is and query it directly. I also use kloth.net where you can set what DNS server you use. The problem is 100% discount domains. You request a change and they think about it and do it about 90 minutes later. I switched all of my Domains I manage from DD to metaname the minute I got a sniff of issues there and I'm really glad I did as they've had multiple long outages since then where their DNS just stops working. With Metaname I request a change - Check it 10 seconds later and its live on the Metaname servers. I know full well how TTL's work but none of that is any use at all if the root server hasn't updated. Using 'kloth.net' or 'MXtoolbox' means you're using web-based versions of tools you could easily run yourself. The people saying 'use dig or similar commands' have not understood that you're getting the same result if you're setting the parameters of kloth.net (which is a web interface for dig) correctly. If the web interface for modifying zone records at DD only pushes its changes out at intervals, you're stuck. The only people who'll know how this works, are DD and their web-based help resources are crap - as you say. I moved all the domains I operate away from Discount Domains some years ago when they kept trotting this out like it was gospel. The main advice I have is: Prior to making changes, query the SOA record directly against both the primary and secondary DNS servers and record the serial number Post making the changes, repeat and see if the serial has changed (if it hasn't, then the file is not recorded as having changed from the nameserver's POV Once you see the serial number change, an update has been pushed. TTL's will of course only impact recursive servers that are holding cached information; authoritive NS will see the change as soon as they receive and reload the zone file and/or receive zone transfer from the master. The further advice I have, is vote with your feet/wallet: reward service providers who know what they're doing. Abandon those who don't. I could run the tools myself but I might be on my work office pc, my home office pc, a clients pc, my phone or my iPad and these web tools work well from any of them. Also considering I use them on average a couple of times a month at most using a web tools rather than a local tool is actually easier. i agree on voting with feet and I did that very early in the picture at first sign of issues. Never regretted it as metamame does everything I need/want and doesn’t try to bundle a bunch of services I don’t want and it just works flawlessly. Just on an aside to show how it should work. I registered a brand new .co.nz domain name and was able to create the TXT records to validate the domain with Microsoft, setup a new 365 mailbox and create the other txt, cname and MX records and it was all up and running in 25 minutes. It took about 20 minute from the domain being registered and the DNS servers switching from the Internet NZ Registery ones to Metaname and everything else was instantaneous. Compare that to waiting 90 minutes for a cname record change with DD. Many years ago (many, many years ago) when I was working for a service provider I won't name, DNS changes would only sync with production every few hours as part of a scheduled sync of 'config app' vs 'zone files on unix server'. This is just evidence of the fact there are providers out there running 'old stuff'. Can only again suggest avoiding the providers who still run sluggish (by todays standards) infrastructure and don't have customer service reps who actually understand the way things work (I saw someone else quote the '48-72 hours' numbers today, i nearly saw red, lol) If you have access to their DD account just move the DNS zone to cloudflare and update the name servers. The domain stays where it is so they pay the bills to DD as before but you get much better DNS control. Its like my wife - "I'm not asking you to solve it. I just want your sympathy" 🤣 It should just never be that bad. I am thinking about shifting them but its an org I prefer them actually retaining ownership completely. Most of my clients I just leave the domain all in their name etc but put it in my account at metaname and manage it so I know it'll be renewed etc. Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.