21–30 of 43 posts
Status in whois response is “active” for me, and he.net resolves from DNS for me, so I guess it’s been fixed? But why did they list a @he.net email address as one of the emails to contact them on? Wasn’t the problem that he.net would not resolve because of that very client hold?
I can't believe that NetworkSolutions doesn't have a list of significant ISPs by domain name or something. I would proactively work with significant ISPs before suspending the entire domain and interrupting their services.
The fact that their netops / support staff have no way to escalate an issue like this is the bigger issue. IMHO the giant ISP shouldn't get a better response time or procedure; everyone should be able to get help in an emergency like this.
Really, NANOG have themselves to blame. Half the reason NANOG was started was to help high level techies bypass low-level operations/support staff.
Everyone should have worked together to make sure their own orgs could appropriately handle calls/issues like this.
Instead, with the issue mostly fixed for them, they stopped caring, and all the peons and techies who don't work for Fortune 500 or famous tech companies are still fucked...
I can't believe that NetworkSolutions doesn't have a list of significant ISPs by domain name or something. I would proactively work with significant ISPs before suspending the entire domain and interrupting their services.
NetSol should've done better though, this makes them look like clowns.
Status in whois response is “active” for me, and he.net resolves from DNS for me, so I guess it’s been fixed? But why did they list a @he.net email address as one of the emails to contact them on? Wasn’t the problem that he.net would not resolve because of that very client hold?
I can't believe that NetworkSolutions doesn't have a list of significant ISPs by domain name or something. I would proactively work with significant ISPs before suspending the entire domain and interrupting their services.
There's a reason people were practically partying in the streets when Network Solutions lost their monopoly. The fact that their netops / support staff have no way to escalate an issue like this is the bigger issue. IMHO the giant ISP shouldn't get a better response time or procedure; everyone should be able to get help in an emergency like this. Really, NANOG have themselves to blame. Half the reason NANOG was start…
I can't believe that NetworkSolutions doesn't have a list of significant ISPs by domain name or something. I would proactively work with significant ISPs before suspending the entire domain and interrupting their services.
Its not really going to affect their services, maybe email in/out of it but thats about it. NetSol should've done better though, this makes them look like clowns.
idk. how do you know that their management capability can run sans dns?
I can't believe that NetworkSolutions doesn't have a list of significant ISPs by domain name or something. I would proactively work with significant ISPs before suspending the entire domain and interrupting their services.
There's a reason people were practically partying in the streets when Network Solutions lost their monopoly. The fact that their netops / support staff have no way to escalate an issue like this is the bigger issue. IMHO the giant ISP shouldn't get a better response time or procedure; everyone should be able to get help in an emergency like this. Really, NANOG have themselves to blame. Half the reason NANOG was start…
Status in whois response is “active” for me, and he.net resolves from DNS for me, so I guess it’s been fixed? But why did they list a @he.net email address as one of the emails to contact them on? Wasn’t the problem that he.net would not resolve because of that very client hold?
Confirmed at 3:30 CT
Still not sure if the status it shows in Whois means that it’s resolved or not.
Earlier quoted context omitted.
Its not really going to affect their services, maybe email in/out of it but thats about it. NetSol should've done better though, this makes them look like clowns.
> Its not really going to affect their services, maybe email in/out of it but thats about it idk. how do you know that their management capability can run sans dns?