APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

Control your domain registration data

Your domain registration is critically important. It's easy to get lazy about this stuff. Often your ISP or whoever set up your web site said they'd "take care of it" and that was it. It's been working fine for years, and you don't have to worry about it.

You may want to read this slightly less technically oriented version why controlling your domain registration is important.

But you do need to worry about it. In fact, you need to take control of it, and review that control regularly to make sure you still have it. If you lose control, it can be time consuming and difficult to get it back - in fact, you could even lose your domain name, though that's not the subject discussed here.

If you are totally confused by DNS, I recommend Take Control of Your Domain Names, a $10.00 PDF E-Book that demystifies all of this.

Let's review DNS for a moment. This is external DNS, not the DNS you may be using inside your own network to identify machines. This DNS is the one that lets you get mail if you have a mail server and lets people get to your website. It is extremely important. Yes, it's geek talk, you don't want to hear it, let somebody else take care of this, but it's too important for that. You need to understand this or everything can come to a grinding halt.

Your web site is registered with one of the official registrars. From your point of view, you may have paid money to someone else for the domain registration, but it's one of these places that really did the work, and there is one critical piece of information they control about your domain. That piece of data is the address of the name servers responsible for resolving addresses in your domain. So, if you are xyz.com, somewhere there is a name server that knows where www.xyz.com is, where mail.xyz.com is and so on. The registrar doesn't necessarily know or care where www.xyz.com is, but they do have to know who does know that.

Life used to be more simple. There was one, and exactly one registrar: Network Solutions. You did the domain registration with them, and that was it. Actually, there was a time when it was even more simple, but from your point of view, somewhere there is a database that keeps track of you and me and everyone else. It isn't your registrar who actually keeps that database, but they are allowed to access it to update information. So that's the flow: your registrar knows where your DNS servers are, and they tell the central servers. The overall control of all this is now in the hands of ICANN.

Do we have the picture now? Your ISP may actually provide DNS information, but it's the registrar who tells the central DNS to go ask your ISP for IP addresses and reverse lookups. If the registrar told the central servers that a different outfit was responsible for your domain, that's where the ip address for www.xyz.com would come from.

This is important, so I'm going to be pedantic here just in case you aren't getting this yet. Let's say that the DNS server at worldnic.com says that your www address is and the DNS server at your ISP says it's Which address will you get if you "ping www.xyz.com"?

The answer depends on who your registrar says is your DNS server. If they say worldnic is responsible, then your ping will go to, but if they say your ISP's servers are the authority for your domain, then it goes to Two different addresses, and possibly different web sites.

You can use "dig" to query specific nameservers: dig @somedns xyz.com. That bypasses your normal DNS and directly asks the server you specify

So now for the really important question. Who controls the registrar?

If the answer isn't "I do", then you have a problem. Is it the guy who designed your web site? Who was that guy, anyway? Or maybe it's the ISP who unfortunately just went out of business and isn't answering the phone any more. You "own" your domain, and want to move it to a new ISP, but how's that going to happen if you don't control the registrar?

Well, it can be difficult. You are going to have to prove that you really do own xyz.com, that the guy who designed the site or the defunct ISP was just acting on your behalf, and then you can tell the registrar where to point your DNS (or can control it yourself right at the registrar; for example Network Solutions allows you to maintain your own DNS).

You may actually already have an account with the registrar. That may have been setup for you when you first created your domain. When you set up an account, they usually want an email address for you. That address is important, because usually that's all they need to prove your identity later: they just send a query to the address they have for you, and if you can respond to it, well, that's you then. But what if the email address you used was an old aol account that you let lapse? They can't send mail to it, so you can't prove you own the domain that way.

There are, of course procedures for this kind of situation. You may be able to fax a simple form that sets the domain registration information straight. It obviously shouldn't be too easy: you wouldn't want someone to be able to steal your domain or divert it elsewhere simply by saying "that's mine".

There have been cases of hijacking, including the famous "sex.com" dispute. If you have the wrong people listed in the "whois" for your domain, it can be dangerously easy.

By the way, you also need to watch out for these fly by night and fake domain renewals. Know who you are supposed to renew your domain with so you don't get caught by one of these folks. I have had more than one client think that they renewed but actually they just paid money for some valueless "listing service" masquerading as domain renewal.

The time to get it all sorted out is before you need to. You don't want to find out you have a problem with your registrar on the day your ISP goes belly up or when someone tries to hijack your domain name. So.. take a moment now to dig into this. If you don't know who has control of your registrar, find out. If it is you, make sure you have account names and passwords and that any information they have about you (email, postal address, phone) is current and accurate.

Controlling your domain registration and DNS with your registrar is important; Look into it today.

Got something to add? Send me email.

(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

-> -> Control your domain registration data


Increase ad revenue 50-250% with Ezoic

More Articles by

Find me on Google+

© Tony Lawrence

Tue Aug 23 16:25:59 2005: 1011   rbailin

The answer depends on who your registrar says is your DNS server. If they say worldnic is responsible, then your ping will go to, but if they say your ISP's servers are the authority for your domain, then it goes to Two different addresses, and possibly different web sites.

Actually, it depends on who you use for a DNS server. If you use your ISP's DNS server(s), you'll get the 82.x site, assuming they ignore DNS updates pertaining to their own sites. If you use anyone else's DNS server, you'll get the 64.x version.


Tue Aug 23 17:55:14 2005: 1012   TonyLawrence

Well, that's the case where you happen to be pointing your DNS where you think the world is going to look. That can be confusing, but the important thing for the rest of the world is what the registrar says is the authoritative server for your domain.

But as Bob notes, I've seen people get bollixed up by this too: their domain is really served by xyz.com, but they have records at abc.com AND use abc.com as their local networks DNS server. So, depending on which is correct (abc or xyz) either they (and anyone else using abc) get the right site and the rest of the world gets sent to the wrong site that xyz has. world - or vice versa.

Kerio Samepage

Have you tried Searching this site?

Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us

What happens then? Is there a ticker tape parade and heartfelt thanks from the computer it has reached? No, my friends, there is not. The poor packet is immediately gutted, stripped of its protective layers and tossed into the hungry maw of whatever application (mail, a webserver, whatever) it belongs to. (Tony Lawrence)

This post tagged: