Enom Hosted Custom Domains 1 Time Again Showing Intermittent Connectivity Issues
Monday, June 17, 2019
Edit
This week, nosotros convey a few reports inwards Blogger Help Forum: Something Is Broken, nearly active in addition to mature domains, all of a abrupt stopped working.
As we reported final year, the Google partner registrar eNom occasionally has a work amongst their DNS server complement. Right now, 1 of their DNS servers appears consistently bad.
Using a comprehensive Dig tool, nosotros tin discovery a given domain, in addition to compare the DNS addresses existence served yesteryear all authoritative bring upwards servers for a given domain, inwards a unmarried transaction.
Here's a hypothetical example, of what we're seeing correct now, for several eNom hosted domains.
It's possible that this work volition touching to a greater extent than eNom customers, equally the solar daytime progresses, cached DNS addresses expire, in addition to readers of diverse eNom hosted domains asking DNS addresses. I promise that eNom Customer Service tin react to this work to a greater extent than promptly than they convey reacted to the instantly previous problem.
Watch for eNom acknowledged changes in addition to problems.
I convey used my domain amongst no problems, since final year. Today, it all of a abrupt stopped working, in addition to the browser reportsOops! Google Chrome could non discovery www.mydomain.com.I asked my friends nearly my domain - in addition to they enjoin me that my weblog is inaccessible to them, also. I didn't modify whatever settings - in addition to it was fine, until final night.
As we reported final year, the Google partner registrar eNom occasionally has a work amongst their DNS server complement. Right now, 1 of their DNS servers appears consistently bad.
Using a comprehensive Dig tool, nosotros tin discovery a given domain, in addition to compare the DNS addresses existence served yesteryear all authoritative bring upwards servers for a given domain, inwards a unmarried transaction.
Here's a hypothetical example, of what we're seeing correct now, for several eNom hosted domains.
mycustomdomain.com@dns1.name-services.com.: mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21 mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21 mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 mycustomdomain.com@dns2.name-services.com.: mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21 mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21 mycustomdomain.com@dns3.name-services.com.: mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21 mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21 mycustomdomain.com@dns4.name-services.com.: mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21 mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 mycustomdomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21 mycustomdomain.com@dns5.name-services.com.: org. 3601 IN SOA dns1.name-services.com. info.name-services.com. 2010 10800 3600 604800 3600 www.mycustomdomain.com@dns1.name-services.com.: www.mycustomdomain.com. 1800 IN CNAME ghs.google.com. www.mycustomdomain.com@dns2.name-services.com.: www.mycustomdomain.com. 1800 IN CNAME ghs.google.com. www.mycustomdomain.com@dns3.name-services.com.: www.mycustomdomain.com. 1800 IN CNAME ghs.google.com. www.mycustomdomain.com@dns4.name-services.com.: www.mycustomdomain.com. 1800 IN CNAME ghs.google.com. www.mycustomdomain.com@dns5.name-services.com.: org. 3601 IN SOA dns1.name-services.com. info.name-services.com. 2010 10800 3600 604800 3600Right now, it appears that server "dns5" is consistently broken.
It's possible that this work volition touching to a greater extent than eNom customers, equally the solar daytime progresses, cached DNS addresses expire, in addition to readers of diverse eNom hosted domains asking DNS addresses. I promise that eNom Customer Service tin react to this work to a greater extent than promptly than they convey reacted to the instantly previous problem.
Watch for eNom acknowledged changes in addition to problems.