Want to understand more about nameservers

I'm pretty dim with much of this technical stuff. Fact is i haven't had to learn, so i haven't.

I'd like to know what the real differences are between using your hosts nameservers, and using personal ones. A pro's and cons list for each would be cool.

I'd also like to know if the domain extension has any effect, ie .com versus .co.uk. If it does i'd like to know why, and which is better.

I've tried seareching for 'nameserver' related terms, but the results are all hosting companies explaining nothing.

Cheers for any help

>I'd like to know what the real differences are between using your hosts nameservers, and using personal ones. A pro's and cons list for each would be cool.

If you’re using your personal and you actually have no real control over the name servers, then they just look cool and have no function other than looking nice. If you actually run your own name servers then that's a different matter.

>I'd also like to know if the domain extension has any effect, ie .com versus .co.uk. If it does i'd like to know why, and which is better.

Should make no odds, I used .co.uk as I can easy update them very quickly with direct access to Nominet database, however .com is not much different really so it's your choice.

At present my name servers are like this

1 in London and in New York. (a 3rd from British Columbia in Canada to be added shortly)

I use the name server’s ns1.internetbackbone.co.uk and ns2.internetbackbone.co.uk, they are on totally different IP blocks, ISPs and world regions, so if one location was to go down, my sites in other locations will keep working.

www.ukinternetsites.com and www.ukinternetsites.co.uk are in different locations, so I should always be able to be contacted.

Most companies have name servers in the same place. This is a bad idea if you ask me, however if you have no servers out side your current location and your systems go down, what can you do anyway.

One other thing that I am going to do, is actually have different domains, on different extensions from different name companies, this way you don't have a situation when your domain name is not renewed, all your sites go off line, however touch wood this will never happen, but best to be careful.

Thanks Supercod,

I'm just trying to understand what caused this latest problem, and more importantly, what i can do to stop it from happening again.

<blockquote><strong><em>Quote:</em></strong><hr>If you’re using your personal and you actually have no real control over the name servers, then they just look cool and have no function other than looking nice. If you actually run your own name servers then that's a different matter.[/quote]

That answered most of my question i think.

<blockquote><strong><em>Quote:</em></strong><hr>Should make no odds, I used .co.uk as I can easy update them very quickly with direct access to Nominet database, however .com is not much different really so it's your choice.[/quote]

That part helped confuse me though. The following statements are from the hosting support board:


<blockquote><strong><em>Quote:</em></strong><hr>This was a very complex DNS issue.
We changed your name server IP's but the glue records on the Nominet name servers had not been updated.
These are only required when a .co.uk domain is hosted on name servers which use the same.

This has been fixed and your domain will start to come back up.[/quote]

and

<blockquote><strong><em>Quote:</em></strong><hr>Its because you use a .co.uk domain for your name servers
If you used a .com it would not have happened.[/quote]

:|

It can't have just been the glue record only as that's not in the slightest complex.

www.nic.uk/TagHolders/Usi...onFaq/#1.5

Unless they mean it's complex in that they don't want to explain as you won't have a clue what they are talking about that's not meant in a cheeky way as not setting the glue can make it not work, just that's not complex, takes 2 seconds to correct, however you need to wait for the next Nominet reload, this happened every 24 hours, unless you are eBay.co.uk and you get it done on demand.

.com do need to have an IP assigned to them when it's for a name servers, otherwise you don't need to, but most registers still ask for it anyway.

<blockquote><strong><em>Quote:</em></strong><hr>Unless they mean it's complex in that they don't want to explain as you won't have a clue what they are talking about that's not meant in a cheeky way[/quote]

This wouldn't in the least surprise me. I have said a couple of rather funny things in the past , but i'd rather ask than never know.

The site is now back for some people. As of 10am i started getting subscriptions again, all hotmail and aol funny enough.

I can access the site using it's IP, but no other way.

Unfortunately the other 2 sites concerned show no such signs of improvement. But i'm guessing that until the master account is fully operational again, the sub-accounts don't have a chance.

Last question :O)

Could this have happened anywhere, or is it lax? I realise you might be a little uncomfortable answering that, but i'm sure you'll find a way to answer LOL

I am looking at investing quite a lot on this side of things, and i'd like as much info as possible. If the problem is 'beyond my understanding', your general feeling won't be

They say that if your nameserver records have the same TLD as your domain then it does give slightly quicker connections.


<hr />
This means that they are supplying the NS records (host.example.com), but not supplying the A records (127.0.0.1), which can cause slightly slower connections, and may cause some incompatibilities with some programs. This behavior is allowed by the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.co.uk" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.
<hr />

Taken from dnsreport.com