Hacker News new | past | comments | ask | show | jobs | submit login

Disclaimer: I work for a web hosting company. They are NOT affiliated in any way with name.com

The problem is that you don't understand how domain parking works. If you want to just own a domain but don't want it to go anywhere yet, you need to make records for that. "Domain parking" is the shady practice of putting up a "palceholder" page filled with ads.

Also...you don't know what "NXDOMAIN" is / means. Here are the RFCs:

http://www.ietf.org/rfc/rfc2308.txt -- " "NXDOMAIN" - an alternate expression for the "Name Error" RCODE as described in [RFC1035 Section 4.1.1] and the two terms are used interchangeably in this document."

http://www.ietf.org/rfc/rfc1035.txt "RCODE Response code - this 4 bit field is set as part of responses. The values have the following interpretation:

                0               No error condition

                1               Format error - The name server was
                                unable to interpret the query.

                2               Server failure - The name server was
                                unable to process this query due to a
                                problem with the name server.

                3               Name Error - Meaningful only for
                                responses from an authoritative name
                                server, this code signifies that the
                                domain name referenced in the query does
                                not exist."
That's right, NXDOMAIN = "domain name referenced in the query does not exist", which is FALSE in this situation, so why would their DNS server return that?

Name.com provides a FREE nameserver service which happens to have some strings attached. If you don't use their FREE DNS hosting service, those strings are NOT attached. I have been using name.com for years and have never had any problems. They don't do the same BS that places like Network Solutions do where they monitor what domains people are searching for an increase the prices based on that.

Seriously, learn what you're talking about before bashing a company publicly as much as this. I'm sure that a quick call or e-mail (also, who sends an e-mail requesting that a company call them? Protip: people in tech support HATE that...just ask your question in the e-mail) with a properly-worded question like "Yo, why does my domain name NOT return an 'nxdomain' code when I query your nameserver?" would have resulted in a clear and concise answer from them.

Is it BS that ads are put on parked domains? Sure, but then again, YOU DON'T HAVE TO PARK A DOMAIN.




From the article

"at a non-existent subdomain of Typewire's site"

Surely a non-existent subdomain should return a Name Error?

Unless you explicitly asked for a wildcard subdomain (which I realize the T&Cs _say_ you did, even though you never intended too), then I'd expect ww.realdomain.com and qqq.realdomain.com to return NXDOMAIN.

(and I agree with the post, adding a wildcard domain and putting ads on the parked pages is nasty, insisting it's a core part of your business model when called on it is evil, trying to then claim I'm somehow responsible for the ad content on this pages is beyond stupid! I'd certainly never use a registrar that chose to do that to me.)


i'm confused. I use name.com free DNS. I didn't park anything and thought I was doing everything right.

  dustingetz.com
  www.dustingetz.com
  adsfkjhasfasdf.dustingetz.com <--- name.com content
I expected it to time out. Name.com shows no * record, but cloudflare showed me this (I think it rotates through a few IPs). I guess I'd have to move off the free DNS to remove the * record.

  A record *	points to	174.37.172.68




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: