Who owns dns entry

Improve this question. Arcsn Arcsn 1 1 gold badge 1 1 silver badge 5 5 bronze badges. Add a comment. Active Oldest Votes. There are three parts to this.

Improve this answer. It says: Reported by b. Now i will check with them. EDIT: it is godaddy. I'll check with them.

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming The answer you got is not authoritative. The result is of your training session of your provider. Other hosters offering such training opportunities might provide you different results, but again not authoritative.

No, you don't need to know that as that domain is just for testing and training for name service, not for web service. Why should there exist a web site for your training session? DNS databases don't need a web interface. Your training should be on the database, not on a web form. We have private registration but whois still shows our registrar and who does our DNS, in this case, Rackspace. As long as you have access to the domain registrar, you can always repoint the nameservers for the domain to any other DNS host or web host you have access to if necessary.

This is usually an indication that your user is not authorized to change external DNS configuration. If this is the case, then you don't need to identify the external DNS hoster nor its owner. You need instead use a whois request to find the contacts for change. And as regulations on whois are contradictory, you may come across organisatons subject to jurisdiction where disclose of direct contacts is not mandatory and requires additional optional consents. If such consents don't exist or don't meet changed legal requirements, you still find contact info there which is usually a contact within the registrar.

In such cases, you may ask your customer to disclose the contact info to you or refer him to the person within his organisation. So if you want your customers to change DNS info, why do you want to force those in charge of DNS configuration to first establish a web interface even for cases where their contracts and instructions direct you otherwise, like informal data exchange with approval by agreed media, a support phone contact, or the new text record?

The organisation has a contract for one or several domains. If your user is not involved in that contract, you'll need to find these persons in the user organisation or direct those to find these persons within their own organisation. And if the other party of the contract has decided to outsource DNS management and operation, why do you want to direct your users directly to that 3rd party which usually has no direct relation with your user nor his organisation and hence is not authorized to accept orders for change by the user but instead only by his outsourcing contract partner.

Or there exist cases where the contract partner is a virtual organisation representing a cooperative network. Contracts regulate their customer relation and their internal cooperation. So do you mean you want to test if you're able to steal assinged domains by checking if these 3rd parties accept unauthorized changes?

See my example above. Which is in the WhoIS info. This will work in your case since you're technical enough to know it.

Our goal is to cater non-technical clients who probably hired a consultant to setup their domain initially and the company owner has no idea how to do it. We want to tell such non-technical users where to do go to add a TXT record.

This can be done if there was a definitive way to associate a host name of a Name Server with a company and I am wonder if there is a database some where on the Internet that can give me this information. Get answers from your peers along with millions of IT pros who visit Spiceworks. Popular Topics in DNS. Which of the following retains the information it's storing when the system power is turned off? For most web users, this is all they need to know about the basics of DNS.

A quick warning before you dive in: changing DNS records will affect how your website is accessed. Read everything below and do more research before making your first changes.

The first important piece of information is domain registrars. These entities operate a master list of all the domains registered with their company. When someone buys a URL for their website, they have to go through a registrar.

There are thousands of accredited registrars all across the globe. Many offer web hosting services along with domain registry, so for most intents and purposes, users can consider them one and the same. Domain registrars are where all of the action gets recorded. They usually follow this pattern and come in groups of two or three:.

Nameservers are the most time-consuming part of the DNS records process. When you register or change a domain you might see a message stating that the URL may not work for a few hours or even a day or two. This is because nameservers have to propagate the DNS records to servers across the world before they can recognize a typed website address and translate it to the assigned IP address.

Check out how easy you can set up your nameservers at Presslabs to benefit from our automatic failover and geo serving of the content system. Want to see just how far your DNS information has been propagated?

One of the first stumbling points for new users is learning to identify zones and records. All of a sudden there are dozens upon dozens of complicated acronyms and indecipherable names. DNS records are single entries that give instructions on handling received requests. They only provide an initial validation of the information before passing it on to zones.

Zones, then, are custom-purposed record systems that handle specific and non-standard requests. Think of it like a basic filtering system; records gather all the information and sort it to individual zones for processing.