<div dir="ltr"><div class="gmail_default" style="font-size:small;font-family:garamond,serif">Not sure this is related, but ICANN recently enacted (IMHO this was very ham-fisted and poorly thought out) contact validation rule for registrars that required contacts be validated - with the consequence of failing to validate being that the DNS stop working on a given name.</div>
<div class="gmail_default" style="font-size:small;font-family:garamond,serif"><br></div><div class="gmail_default" style="font-size:small;font-family:garamond,serif">It was mostly so that TM/LEA could find bad actors or at least as a means to ensure the bad actors would receive and validate their response of emails. Logic was that domains for a given contact would go out of delegation which should somehow make the internet safer.</div>
<div class="gmail_default" style="font-size:small;font-family:garamond,serif"><br></div><div class="gmail_default" style="font-size:small;font-family:garamond,serif">Many notices for validation are getting lost in spam filters or not even delivered, and the consequences of having a site go dark are starting to increase.</div>
<div class="gmail_default" style="font-size:small;font-family:garamond,serif"><br></div><div class="gmail_default" style="font-size:small;font-family:garamond,serif">In any event, this may be entirely or slightly related to the issue. </div>
</div><div class="gmail_extra"><br clear="all"><div>Jothan Frakes<br>+1.206-355-0230 tel<br>+1.206-201-6881 fax</div>
<br><br><div class="gmail_quote">On Tue, Apr 22, 2014 at 1:20 PM, Todd Lyons <span dir="ltr"><<a href="mailto:tlyons@ivenue.com" target="_blank">tlyons@ivenue.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On Tue, Apr 22, 2014 at 12:24 PM, Stephane Bortzmeyer <<a href="mailto:bortzmeyer@nic.fr">bortzmeyer@nic.fr</a>> wrote:<br>
> On Tue, Apr 22, 2014 at 12:01:39PM -0700,<br>
> Todd Lyons <<a href="mailto:tlyons@ivenue.com">tlyons@ivenue.com</a>> wrote<br>
> a message of 31 lines which said:<br>
><br>
>> the expiration date is still a ways off, and whois is delegated to<br>
>> the correct DNS. But when we do a dig +trace for that domain, the<br>
>> GTLD servers don't return any NS glue.<br>
><br>
> Do they return NXDOMAIN or something else? Frankly, you do not provide<br>
> enough hard details. The actual output of whois and dig +trace or one<br>
> of these domains would help. There can be many reasons for this sort<br>
> of behaviour (Andrew Sullivan's hypothesis seems very probable).<br>
><br>
<br>
</div>I think Andrew made a good educated guess. The domain that is<br>
currently exhibiting this behavior does have clientHold set. So now<br>
it's up to the client to figure out why their domain got set with<br>
clientHold. Here's the domain info:<br>
<br>
[todd@tlyons ~]$ whois <a href="http://aerosolscience.com" target="_blank">aerosolscience.com</a><br>
<br>
Whois Server Version 2.0<br>
<br>
Domain names in the .com and .net domains can now be registered<br>
with many different competing registrars. Go to <a href="http://www.internic.net" target="_blank">http://www.internic.net</a><br>
for detailed information.<br>
<br>
Domain Name: <a href="http://AEROSOLSCIENCE.COM" target="_blank">AEROSOLSCIENCE.COM</a><br>
Registrar: TUCOWS DOMAINS INC.<br>
Whois Server: <a href="http://whois.tucows.com" target="_blank">whois.tucows.com</a><br>
Referral URL: <a href="http://domainhelp.opensrs.net" target="_blank">http://domainhelp.opensrs.net</a><br>
Name Server: <a href="http://NS1.IVENUE.COM" target="_blank">NS1.IVENUE.COM</a><br>
Name Server: <a href="http://NS2.IVENUE.COM" target="_blank">NS2.IVENUE.COM</a><br>
Status: clientDeleteProhibited<br>
Status: clientHold<br>
Status: clientTransferProhibited<br>
Status: clientUpdateProhibited<br>
Updated Date: 19-apr-2014<br>
Creation Date: 03-aug-2004<br>
Expiration Date: 03-aug-2014<br>
<br>
>>> Last update of whois database: Tue, 22 Apr 2014 20:16:22 UTC <<<<br>
<br>
NOTICE: The expiration date displayed in this record is the date the<br>
registrar's sponsorship of the domain name registration in the registry is<br>
currently set to expire. This date does not necessarily reflect the expiration<br>
date of the domain name registrant's agreement with the sponsoring<br>
registrar. Users may consult the sponsoring registrar's Whois database to<br>
view the registrar's reported date of expiration for this registration.<br>
<br>
TERMS OF USE: You are not authorized to access or query our Whois<br>
database through the use of electronic processes that are high-volume and<br>
automated except as reasonably necessary to register domain names or<br>
modify existing registrations; the Data in VeriSign Global Registry<br>
Services' ("VeriSign") Whois database is provided by VeriSign for<br>
information purposes only, and to assist persons in obtaining information<br>
about or related to a domain name registration record. VeriSign does not<br>
guarantee its accuracy. By submitting a Whois query, you agree to abide<br>
by the following terms of use: You agree that you may use this Data only<br>
for lawful purposes and that under no circumstances will you use this Data<br>
to: (1) allow, enable, or otherwise support the transmission of mass<br>
unsolicited, commercial advertising or solicitations via e-mail, telephone,<br>
or facsimile; or (2) enable high volume, automated, electronic processes<br>
that apply to VeriSign (or its computer systems). The compilation,<br>
repackaging, dissemination or other use of this Data is expressly<br>
prohibited without the prior written consent of VeriSign. You agree not to<br>
use electronic processes that are automated and high-volume to access or<br>
query the Whois database except as reasonably necessary to register<br>
domain names or modify existing registrations. VeriSign reserves the right<br>
to restrict your access to the Whois database in its sole discretion to ensure<br>
operational stability. VeriSign may restrict or terminate your access to the<br>
Whois database for failure to abide by these terms of use. VeriSign<br>
reserves the right to modify these terms at any time.<br>
<br>
The Registry database contains ONLY .COM, .NET, .EDU domains and<br>
Registrars.<br>
Domain Name: <a href="http://AEROSOLSCIENCE.COM" target="_blank">AEROSOLSCIENCE.COM</a><br>
Registry Domain ID: 126329129_DOMAIN_COM-VRSN<br>
Registrar WHOIS Server: <a href="http://whois.tucows.com" target="_blank">whois.tucows.com</a><br>
Registrar URL: <a href="http://tucowsdomains.com" target="_blank">http://tucowsdomains.com</a><br>
Updated Date: 2014-04-03 03:38:31<br>
Creation Date: 2004-08-03 15:15:53<br>
Registrar Registration Expiration Date: 2014-08-03 15:15:53<br>
Registrar: TUCOWS, INC.<br>
Registrar IANA ID: 69<br>
Registrar Abuse Contact Email: <a href="mailto:domainabuse@tucows.com">domainabuse@tucows.com</a><br>
Registrar Abuse Contact Phone: <a href="tel:%2B1.4165350123" value="+14165350123">+1.4165350123</a><br>
Reseller: Netfirms<br>
Reseller: <a href="mailto:support@netfirms.com">support@netfirms.com</a><br>
Reseller: <a href="tel:%2B1.866-317-4678" value="+18663174678">+1.866-317-4678</a><br>
Reseller: <a href="http://netfirms.com" target="_blank">http://netfirms.com</a><br>
Domain Status: clientDeleteProhibited<br>
Domain Status: clientHold<br>
Domain Status: clientTransferProhibited<br>
Domain Status: clientUpdateProhibited<br>
Registry Registrant ID:<br>
Registrant Name: Werner Bergman<br>
Registrant Organization: Aerosol Science<br>
Registrant Street: 6260 Stoneridge Mall Rd. A213<br>
Registrant City: Pleasanton<br>
Registrant State/Province: CA<br>
Registrant Postal Code: 94588<br>
Registrant Country: US<br>
Registrant Phone: <a href="tel:9254696922" value="+19254696922">9254696922</a><br>
Registrant Phone Ext:<br>
Registrant Fax:<br>
Registrant Fax Ext:<br>
Registrant Email: <a href="mailto:wernerbergman@comcast.net">wernerbergman@comcast.net</a><br>
Registry Admin ID:<br>
Admin Name: Werner Bergman<br>
Admin Organization: Aerosol Science<br>
Admin Street: 6260 Stoneridge Mall Rd. A213<br>
Admin City: Pleasanton<br>
Admin State/Province: CA<br>
Admin Postal Code: 94588<br>
Admin Country: US<br>
Admin Phone: <a href="tel:9254696922" value="+19254696922">9254696922</a><br>
Admin Phone Ext:<br>
Admin Fax:<br>
Admin Fax Ext:<br>
Admin Email: <a href="mailto:wernerbergman@comcast.net">wernerbergman@comcast.net</a><br>
Registry Tech ID:<br>
Tech Name: Domains Manager<br>
Tech Organization: Netfirms, Inc.<br>
Tech Street: 5160 Yonge St<br>
Tech City: Toronto<br>
Tech State/Province: ON<br>
Tech Postal Code: M2N6L9<br>
Tech Country: CA<br>
Tech Phone: <a href="tel:%2B1.4166612100" value="+14166612100">+1.4166612100</a><br>
Tech Phone Ext:<br>
Tech Fax: <a href="tel:%2B1.4166610700" value="+14166610700">+1.4166610700</a><br>
Tech Fax Ext:<br>
Tech Email: <a href="mailto:support@netfirms.com">support@netfirms.com</a><br>
Name Server: <a href="http://NS1.IVENUE.COM" target="_blank">NS1.IVENUE.COM</a><br>
Name Server: <a href="http://NS2.IVENUE.COM" target="_blank">NS2.IVENUE.COM</a><br>
DNSSEC: Unsigned<br>
URL of the ICANN WHOIS Data Problem Reporting System: <a href="http://wdprs.internic.net/" target="_blank">http://wdprs.internic.net/</a><br>
>>> Last update of WHOIS database: 2014-04-03 03:38:31 <<<<br>
<br>
Registration Service Provider:<br>
Netfirms, <a href="mailto:support@netfirms.com">support@netfirms.com</a><br>
<a href="tel:%2B1.866-317-4678" value="+18663174678">+1.866-317-4678</a><br>
<a href="tel:%2B1.781-998-8586" value="+17819988586">+1.781-998-8586</a> (fax)<br>
<a href="http://netfirms.com" target="_blank">http://netfirms.com</a><br>
This company may be contacted for domain login/passwords,<br>
DNS/Nameserver changes, and general domain support questions.<br>
<br>
The Data in the Tucows Registrar WHOIS database is provided to you by Tucows<br>
for information purposes only, and may be used to assist you in obtaining<br>
information about or related to a domain name's registration record.<br>
<br>
Tucows makes this information available "as is," and does not guarantee its<br>
accuracy.<br>
<br>
By submitting a WHOIS query, you agree that you will use this data only for<br>
lawful purposes and that, under no circumstances will you use this data to:<br>
a) allow, enable, or otherwise support the transmission by e-mail,<br>
telephone, or facsimile of mass, unsolicited, commercial advertising or<br>
solicitations to entities other than the data recipient's own existing<br>
customers; or (b) enable high volume, automated, electronic processes that<br>
send queries or data to the systems of any Registry Operator or<br>
ICANN-Accredited registrar, except as reasonably necessary to register<br>
domain names or modify existing registrations.<br>
<br>
The compilation, repackaging, dissemination or other use of this Data is<br>
expressly prohibited without the prior written consent of Tucows.<br>
<br>
Tucows reserves the right to terminate your access to the Tucows WHOIS<br>
database in its sole discretion, including without limitation, for excessive<br>
querying of the WHOIS database or for failure to otherwise abide by this<br>
policy.<br>
<br>
Tucows reserves the right to modify these terms at any time.<br>
<br>
By submitting this query, you agree to abide by these terms.<br>
<br>
NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY. LACK OF A DOMAIN<br>
RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.<br>
<br>
[todd@tlyons ~]$ dig +trace <a href="http://aerosolscience.com" target="_blank">aerosolscience.com</a><br>
<br>
; <<>> DiG 9.8.1-P1 <<>> +trace <a href="http://aerosolscience.com" target="_blank">aerosolscience.com</a><br>
;; global options: +cmd<br>
. 157142 IN NS <a href="http://e.root-servers.net" target="_blank">e.root-servers.net</a>.<br>
. 157142 IN NS <a href="http://f.root-servers.net" target="_blank">f.root-servers.net</a>.<br>
. 157142 IN NS <a href="http://g.root-servers.net" target="_blank">g.root-servers.net</a>.<br>
. 157142 IN NS <a href="http://h.root-servers.net" target="_blank">h.root-servers.net</a>.<br>
. 157142 IN NS <a href="http://i.root-servers.net" target="_blank">i.root-servers.net</a>.<br>
. 157142 IN NS <a href="http://j.root-servers.net" target="_blank">j.root-servers.net</a>.<br>
. 157142 IN NS <a href="http://k.root-servers.net" target="_blank">k.root-servers.net</a>.<br>
. 157142 IN NS <a href="http://l.root-servers.net" target="_blank">l.root-servers.net</a>.<br>
. 157142 IN NS <a href="http://m.root-servers.net" target="_blank">m.root-servers.net</a>.<br>
. 157142 IN NS <a href="http://a.root-servers.net" target="_blank">a.root-servers.net</a>.<br>
. 157142 IN NS <a href="http://b.root-servers.net" target="_blank">b.root-servers.net</a>.<br>
. 157142 IN NS <a href="http://c.root-servers.net" target="_blank">c.root-servers.net</a>.<br>
. 157142 IN NS <a href="http://d.root-servers.net" target="_blank">d.root-servers.net</a>.<br>
;; Received 512 bytes from 192.168.100.10#53(192.168.100.10) in 19 ms<br>
<br>
com. 172800 IN NS <a href="http://k.gtld-servers.net" target="_blank">k.gtld-servers.net</a>.<br>
com. 172800 IN NS <a href="http://f.gtld-servers.net" target="_blank">f.gtld-servers.net</a>.<br>
com. 172800 IN NS <a href="http://j.gtld-servers.net" target="_blank">j.gtld-servers.net</a>.<br>
com. 172800 IN NS <a href="http://b.gtld-servers.net" target="_blank">b.gtld-servers.net</a>.<br>
com. 172800 IN NS <a href="http://a.gtld-servers.net" target="_blank">a.gtld-servers.net</a>.<br>
com. 172800 IN NS <a href="http://m.gtld-servers.net" target="_blank">m.gtld-servers.net</a>.<br>
com. 172800 IN NS <a href="http://g.gtld-servers.net" target="_blank">g.gtld-servers.net</a>.<br>
com. 172800 IN NS <a href="http://i.gtld-servers.net" target="_blank">i.gtld-servers.net</a>.<br>
com. 172800 IN NS <a href="http://c.gtld-servers.net" target="_blank">c.gtld-servers.net</a>.<br>
com. 172800 IN NS <a href="http://e.gtld-servers.net" target="_blank">e.gtld-servers.net</a>.<br>
com. 172800 IN NS <a href="http://h.gtld-servers.net" target="_blank">h.gtld-servers.net</a>.<br>
com. 172800 IN NS <a href="http://l.gtld-servers.net" target="_blank">l.gtld-servers.net</a>.<br>
com. 172800 IN NS <a href="http://d.gtld-servers.net" target="_blank">d.gtld-servers.net</a>.<br>
;; Received 496 bytes from 2001:dc3::35#53(2001:dc3::35) in 555 ms<br>
<br>
com. 900 IN SOA <a href="http://a.gtld-servers.net" target="_blank">a.gtld-servers.net</a>.<br>
<a href="http://nstld.verisign-grs.com" target="_blank">nstld.verisign-grs.com</a>. 1398197799 1800 900 604800 86400<br>
;; Received 112 bytes from 192.43.172.30#53(192.43.172.30) in 150 ms<br>
<div class="im HOEnZb"><br>
--<br>
The total budget at all receivers for solving senders' problems is $0.<br>
If you want them to accept your mail and manage it the way you want,<br>
send it the way the spec says to. --John Levine<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
dns-operations mailing list<br>
<a href="mailto:dns-operations@lists.dns-oarc.net">dns-operations@lists.dns-oarc.net</a><br>
<a href="https://lists.dns-oarc.net/mailman/listinfo/dns-operations
dns-jobs" target="_blank">https://lists.dns-oarc.net/mailman/listinfo/dns-operations<br>
dns-jobs</a> mailing list<br>
<a href="https://lists.dns-oarc.net/mailman/listinfo/dns-jobs" target="_blank">https://lists.dns-oarc.net/mailman/listinfo/dns-jobs</a><br>
</div></div></blockquote></div><br></div>