Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HE.net problem

mailman.nanog.org

Post reply on HN
Print view View original

11–20 of 43 posts

Re: HE.net problem

#11

Post by [deleted] »

LinuxBender wrote: post #4
bediger4000 wrote: post #2

Is there some context that would aid in understanding this? Because it doesn't make sense.

Looking to see what escalation numbers I may still have... [Edit]: Sent them what I have but it isn't much. Most human contacts have been replaced by menu's. I hope the last one I sent helps. It appears someone managed to get NetworkSolutions (now web.com) to put the domain he.net on clientHold for one Phishing complaint, unrelated to he.net meaning someone did a lookup on bgp.he.net and reported he.net instead of th…

[deleted]

Re: HE.net problem

#12

Post by LinuxBender »

[deleted] wrote: post #11
LinuxBender wrote: post #4

Earlier quoted context omitted.

Looking to see what escalation numbers I may still have... [Edit]: Sent them what I have but it isn't much. Most human contacts have been replaced by menu's. I hope the last one I sent helps. It appears someone managed to get NetworkSolutions (now web.com) to put the domain he.net on clientHold for one Phishing complaint, unrelated to he.net meaning someone did a lookup on bgp.he.net and reported he.net instead of th…

[deleted]

I was with Network Solutions from 1997 to 2023. They were bought by web.com in 2018. They keep the name on the old domain and don't redirect to web.com because they have some non-API automation in place on the old domain.

Re: HE.net problem

#13

Post by qual »

LinuxBender wrote: post #12
[deleted] wrote: post #11

Earlier quoted context omitted.

[deleted]

I was with Network Solutions from 1997 to 2023. They were bought by web.com in 2018. They keep the name on the old domain and don't redirect to web.com because they have some non-API automation in place on the old domain.

Wikipedia has it incorrect then, as they list it as "formerly web.com" ("Network Solutions, LLC, formerly Web.com is an American-based technology company"). Thanks for the clarification!

Re: HE.net problem

#15

Post by toast0 »

trvrprkr wrote: post #3
bediger4000 wrote: post #2

Is there some context that would aid in understanding this? Because it doesn't make sense.

Hurricane Electric (HE) provides, among other things, DNS services. When a domain is placed in `clientHold`, as has happened to HE due to a spurious phishing report, it causes the domain to no longer resolve. So the DNS records for HE and all of HE's customers are gradually becoming unresolvable as caches expire.

Edit: since the domain is fixed, this isn't reproducable anymore.

An interesting thing is that if you have a .net domain with he.net nameservers, the .net authoritative servers will give you full glue records with the A/AAAA for nsX.he.net. But if you ask for he.net, you get back NXDOMAIN.

Example domain removed; no longer relevant.

NetworkSolutions is a truly terrible registrar, and anyone who still has a domain there should use this occasion to switch to somewhere better, which is almost anywhere. IMHO, it may be worthwhile for a real business where their domain is important to move to an expensive corporate registrar like MarkMonitor or CSC, and looking into registry lock, etc.

Re: HE.net problem

#16

Post by codetrotter »

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?

Re: HE.net problem

#17

Post by fragmede »

LinuxBender wrote: post #4
bediger4000 wrote: post #2

Is there some context that would aid in understanding this? Because it doesn't make sense.

Looking to see what escalation numbers I may still have... [Edit]: Sent them what I have but it isn't much. Most human contacts have been replaced by menu's. I hope the last one I sent helps. It appears someone managed to get NetworkSolutions (now web.com) to put the domain he.net on clientHold for one Phishing complaint, unrelated to he.net meaning someone did a lookup on bgp.he.net and reported he.net instead of th…

> As a side note, I recently transferred all my domains away from NetSol/web.com as they lost the ability to define custom name servers

FFS is that what happened? They recently bought the registrar I use and a domain of mine with custom nameservers isn't working and I haven't had a chance to troubleshoot.

Re: HE.net problem

#19

Post by LinuxBender »

fragmede wrote: post #17
LinuxBender wrote: post #4

Earlier quoted context omitted.

Looking to see what escalation numbers I may still have... [Edit]: Sent them what I have but it isn't much. Most human contacts have been replaced by menu's. I hope the last one I sent helps. It appears someone managed to get NetworkSolutions (now web.com) to put the domain he.net on clientHold for one Phishing complaint, unrelated to he.net meaning someone did a lookup on bgp.he.net and reported he.net instead of th…

> As a side note, I recently transferred all my domains away from NetSol/web.com as they lost the ability to define custom name servers FFS is that what happened? They recently bought the registrar I use and a domain of mine with custom nameservers isn't working and I haven't had a chance to troubleshoot.

I doubt they have fixed it and I doubt they have plans to, but in the off chance they have make sure it is prefixed with dns(number) or ns(number) as they will not give you a useful error message if you have not done so. e.g. ns0.yourdomain.tld but that probably won't work either. I used to use bare apex domains for a couple decades but they and several other registrars stopped supporting that. They do not give useful error messages to the clients or to their support. AFAIK there is nobody left that knows how to debug the back-end.

This is just a suggestion but I would consider moving the domains somewhere else. It seems web.com is just hoovering up registrars but not migrating everything to a centralized, modern, maintained system. In my experience and opinion they do not know how the back-end of the old Network Solutions systems work.

Re: HE.net problem

#20

Post by fragmede »

Reviving1514 wrote: post #14
killerstorm wrote: post #8

[flagged]

Please elaborate, how would block chain solve this problem?

If we treat Blockchain as a database with specific properties, and use that to back DNS, then we have a DNS system with those specific properties, instead of the system we currently have, which has different specific properties. Some of those properties are desirable, but as we see here, some of them are not.
Post reply on HN