How To Look Up Domain Names

In the recent debate on how evil Network Solutions is, I neglected to give you the non-evil alternatives.

JumpDomain Whois

The easiest thing to do is go to an old registrar that quit answering my emails so I moved all of my domain names away from them. They had non-existant customer support, so I’m sure they won’t mind us using their tools.

https://domains.jumpdomain.com/whois/whois.cgi

Go to the URL above and put in your domain name. Hit Submit Query. It will also return all of the DNS info. Bookmark that page. I use it all the time. It’s by far the easiest and fastest way to look up available domain names without getting into trouble.

Whois?

First, if you are a Mac user (and I won’t get into that religious debate now), if you go into your utilities folder, there is an application called “Network Utility”. If you open that up, you’ll see all of the tools listed across the top. Click on “Whois”.

You can type in the domain name you want to check on and click on the “Whois” button. It will return all of the DNS info for that domain name or it will say “No match for…” the domain name you are looking for.

Terminal Whois on a Mac

If you are brave, you can open the Terminal application and type in “whois” followed by the domain name. That will also give you the DNS info.

Posted in DNS |

Wikipedia Says Network Solutions Sucks

I really appreciate comments. I really do. I love the interaction with people who use this site. Most of all, I love being right and crushing the opposition.

Network Solutions is waiting for you to search for an available domain name using their site.

With that as background, I got a comment or two from Jack Carlson, who, again, I really appreciate for commenting. He defended NetSol and I had to question if I was right about their practices or not. I know what happened to me and a client of mine. Maybe they saw the error of their ways and changed their practices. I needed to reevaluate.

I checked Wikipedia (and since it’s on the Internet, it must be right of course,) and they also had references that all seem to check out. I think this section below is probably true. It matches my experiences and my client’s. Please click through and read the whole thing.

What do you think? Have you ever had a good or a bad experience with NetSol? Please leave a comment and we’ll all battle it out in the never ending search for the truth.

Network Solutions – Wikipedia, the free encyclopedia

Controversy over domain name front running

There is evidence that there are parties subscribing to this information which are buying some of these domains within milliseconds of them being de-registered.

Network Solutions Inc offer a search engine which permits users to find out if a domain name is available for purchase.[18] Unregistered domain names entered into this search engine are then speculatively reserved by Network Solutions. [18] It should be noted this “reservation” can be removed by anyone immediately by contacting Network Solutions customer service hotline, or it will automatically unreserve within 4 days, allowing the domain to be freely registered anywhere. Also, visitors searching for domain names on their website allow the reservation when they click “OK” on the Reservation Confirmation dialog box. Clicking cancel will prevent the domain name from being reserved.

On January 8, 2008 Domain Name Wire published a story alleging that Network Solutions practices domain name front running.[18] “If you try to register a domain at Network Solutions, but decide not to register it, you won’t be able to register it anywhere else,” the article says.[18] “Network Solutions registers the domain in its company name with the words ‘This Domain is available at NetworkSolutions.com’.”[18] Circle ID reported on January 8, 2008 that Jonathon Nevett, Vice President of Policy at Network Solutions and one of the seven members of the ICANN community who was consulted by the ICANN committee looking at domain tasting abuse,[19] had offered a response to the news story stating Network Solution’s policy.[20] The policy was “a security measure to protect our customers,” said Nevett.[20] “When a customer searches for an available domain name at our website, but decides not to purchase the name immediately after conducting the search,” Nevett added, “after the search ends, we will put the domain name on reserve.”[20] Nevett said that if the domain was “not purchased within 4 days, it will be released back to the registry and will be generally available for registration.”[18]

Posted in web host |

1. Register A Domain Name

DO NOT USE NETWORK SOLUTIONS FOR ANYTHING, EVER!

Registering a domain name is pretty cheap and easy. There are a couple pitfalls that could kill you if you’re not careful, but if you watch out for them, it’ll all be fine.

First, you should understand how the whole DNS thing works. You don’t need to, but it helps to know what you’re doing.

Manage Your Own Domain Name

You might have a technical guy handling all of this computery stuff for you, and that’s cool, but you need to make sure that you have the domain name registered in your name, on your account. You need to have control over the domain name registration as much as you need to have the key to the front door of your house. You need to have the userID and password to the account that manages the domain name.

I’ve heard of people having their developer manage it for them, then running into a conflict with the developer some how and the domain name gets held for ransom. You don’t need to do much with the domain name registration, but when you need to make that one critical change to move to a new web host or a new developer, then you need the keys to that kingdom.

If you set up the registration account, then make sure that your email is the one on file with them. When you share the password with the developer, so he can manage it for you, he’s able to change the password. The only way to protect yourself from that is if you can hit that “Forget your password” link and have the new password emailed to you. Make sure you own everything. Don’t let anyone else help you out with this one. Do it yourself.

Make Sure You Can Transfer It

The other area where you can be vulnerable is with the ability to transfer your domain name to another registrar. The reason that Network Solutions is so evil is that they make you actually call them and listen to a sales pitch before they will release your domain name for transfer. It should be a simple process of logging in, asking for the transfer, responding to some emails and being on your way. It should take 5 minutes to transfer.

My nightmare experience was with JumpDomain. They were great in the old days. They were the cheapest that I could find and the admin interface was powerful adn easy to use. I registered probably 100 domain names with them over the years that I was with them. I recommended them to friends also. (Sorry!)

The trick to transfers is that the registrar has to approve it. They have to send you a code for each domain name. This rule was put in place to prevent unauthorized transfers by bad guys. I appreciate that, but the system better work.

Then, one dark and stormy night, I had a problem with one of the domain names. I opened a help desk ticket on it, asking them to fix the error on their end. No answer. I opened another ticket. No answer. Waited and waited. Sent email. I looked up their WHOIS contact info and sent emails. No response. Over all, I waited a couple months for any kind of response. I did some research and decided to move them all to GoDaddy. I had about 40 names to move at that point.

I finally did some research and found that they were using Enom for their registration. I emailled, then called Enom and explained the situation. They finally emailed me the codes and I was able to transfer them to GoDaddy. Total time to transfer: 3 months.

I learned that prices change and you should always shop around instead of just renewing every year. I learned that the registrar can kill you if they want to, so pick wisely. Admin interfaces can improve, so get the easy to use interface. If you don’t like it, transfer to somewhere else.

GoDaddy seems to be the best and the cheapest, right now. That may change in the next month or two. Network Solutions is horrible. Never, ever, use them. Enom was helpful to me, but they have had some questionable stories told about them. Ask a friend. Ask on line. Ask in forums. Ask me.

Shop around and don’t get bit.

Posted in web site build |

How Does DNS Work?

The Internet is a bunch of computers that all send little packets of data back and forth between each other. The computer that you are reading this on is one of them.

Each computer must have some sort of identifier so that it knows where to send the data to and so that other computer knows where to send it back to. These identifiers are called “IP Addresses”. IP stands for “Internet Protocol”. The address itself looks like this: 63.74.159.145. I’m sure you’ve seen something like that somewhere before.

But when you want a web page, you don’t tell your web browser to go get data from an IP address. You use a “domain name”, like “www.google.com” or “www.walton.com”. That domain name needs to be “resolved”. It’s got to be translated into an IP address so the data knows where to go. That all happens behind the scenes.

I’ll go through all the steps that happen so you’ll know what you need to do to get your own domain name set up without being taken advantage up by low life registrars. More about them later.

When you type in a domain name into your browser and hit enter, your computer goes and asks another server, called a “DNS” or “Domain Name Server” what the IP address is for that domain name. When your computer knows the IP address, it sends off the request and receives that answer back. In this case, the request is for a file that creates the web page in your browser.

Before I go farther, two terms you need to know are “client” and “server”. Each is a computer that can talk to other computers. The difference is that a “client” sends a request, while a “server” responds to requests. One asks and the other answers. Any computer can be either, or both, a client and a server.

Web pages are only one type of request, but probably the most common type. There are time servers that only respond with the time. There are Instant Message servers that sit between two people and send IMs to each of them as they are received. DNS responds to domain names with IP addresses.

So how does that DNS know what IP address is correct? From the “Root Servers”, of course! (No, they don’t serve roots.) There are 13 root servers that contain all of the information for each domain name that has been registered. Yes, they are pretty critical.

When a request for a domain name is received by a root server, it only knows which DNS to go ask for the IP address. DNS servers (Yes, the S is redundant, but who wants to call them “DN servers”?) are also called “name servers”.

Too many technical names? I think I got them all out so I can stop now.

The DNS are located all over. Anyone can have one. I have one here. Anyone can provide the service for you if you really wanted. Now, the DNS manages the relationship between the domain name and the IP address. Root servers know which DNS to ask and the DNS knows the IP. There are local DNS for each computer that needs to look up stuff. There are DNS that have authority over specific domain names.

The root servers get their information from “domain name registrars”. (That’s not really a technical name, so it doesn’t count.) You’ll hear people talking about their “registrar”. GoDaddy.com is one. Networksolutions.com is also one, but they are evil, so NEVER, EVER use them for anything. Did I mention that before?

A registrar will charge you some money per year to register your name. They usually provide a web interface so that you can manage what the name servers are for that domain name. They might provide the DNS for you and they’ll let you manage that too. The strength of that interface and what it will allow you to do is very important.

So, to review, you type in a domain name into your web browser. Your web browser asks the local DNS what the IP address is. If the local DNS doesn’t know, it asks the Root Server, which then tells it which DNS has authority for that name. Your local DNS then asks the DNS with authority, which then responds with the correct IP address. The web browser then sends off the web page request to the proper web server to get the web page.

All of that happens in the blink of an eye, which is a technical term for “under 200 milliseconds”.

Posted in DNS |

How to explain “URLs” so anybody can understand them – easyDNS Blog

How to explain “URLs” so anybody can understand them – easyDNS Blog

One of our tech support guys just had a conversation with somebody who wanted “to register the URL http://example.com/something.html”, where example.com was already registered, the person couldn’t understand why he couldn’t have that URL with “something.html” after it.

We’ve heard variations of this one a lot. Like somebody who knows “xyz.zz” is taken “but can I register “www.xyz.zz?”, no, you can’t.

The easiest way to explain a URL such as this one: http://www.example.com/something.html

Is to think of it as HOW, then WHERE and finally WHAT:

http://	« how?	The method we are going to use to retrieve or “get to” the document described by the URL. Common ones are “http” (Hyper-Text Transfer Protocol), you may also see “ftp://” or “mailto:”
www.example.com	« where?	This is the hostname of the server, somewhere on the internet, which is holding the document we actually want
/something.html	« what?	Finally, after we know what server we are looking for and how we’re going to retrieve the document from it, we now specify exactly which document we want off of the remote server.

Understand those three components and you basically have URLs down cold.

Your web browser (firefox, safari, IE, Opera) is all about “how”, what protocols to use to pull all these documents over the web to your desktop.

The web host is the “what” machine. It sits on a server and serves document after document to remote web browsers who send it requests.

Something has to bridge the browser to the web host/server and that’s the “where”, that’s where DNS and domains come in, and that’s primarily what we do here at easyDNS. We tell web browsers (and other client applications) the “where” aspect of retrieving and transmitting documents (the “whats”) across the internet. We do this via “DNS lookups” …about a quarter billion times a day.

Read the entire article at How to explain “URLs” so anybody can understand them – easyDNS Blog

Posted in web site build |