Nameservers and how they relate to IP's

[thecoalman]

First a little background, when I changed my hosting to here I changed the nameserver iat my registry from :

NS1.OLDNAMSERVER.COM
NS2.OLDNAMSERVER.COM

to:

NS1.MYNAMSERVER.COM
NS2.MYNAMSERVER.COM

I waited 3 days and nothing, I put in support ticket here and they told me that the IP they were pointing to was still wrong? Called up registrar and they changed IP. And it was immedia te change.

I moved another site to my server and same thing, I even asked them on the phone about this and the tech told me they had no control over the IP but obviously something was wrong the last time. If I do a whois query it has correct nameservers but it's still going to older IP.

So what I'm asking is so I don't sit hre waiting is are they giving me the ruin around? Should be noted that the same comapny that owns registarar also owns hosting company.

Secondly it was my assumption that changing the nameservers was all you needed to do?

[JPC-Masood]

Since you have posted in VPS and Dedicated forum, I assume that you have two IPs setup on your vps/server to use for these:

NS1.MYNAMSERVER.COM
NS2.MYNAMSERVER.COM

Have you registered these nameservers using those 2 new IPs at your domain registrar? Can you confirm this info at your domain registrar's control panel? And have you also created A records for your name servers? is your name server up and running with required zones on your vps/server?

[thecoalman]

Since you have posted in VPS and Dedicated forum, I assume that you have two IPs setup on your vps/server to use for these:

Correct

Have you registered these nameservers using those 2 new IPs at your domain registrar?

They only have input box for NS1.MYNAMESERVER.COM and NS2.MYNAMESERVER.COM thats what is in the domain registrar control panel and that is what whois is telling me. Only trouble is its still going to old IP.

And have you also created A records for your name servers? is your name server up and running with required zones on your vps/server?

As far as I know everything is working fine, I have 3 functiong domains on the server. I registered a domain at http://aletianic.com/ a few months ago and that was almost immediately available. Another one that was registered at GoDaddy took less than an hour or two.

Only trouble I had was when I initially moved my original domain and this recent one, both registered at the same company.

I'm guessing the issue is the same as the first one, and the registrar has wrong IP I'm assuming that the listed nameserver is irrellevant if the IP's at the registrar are screwed up? But they are telling me they don't have an input for that but I know full well that it was screwed up on their end before.

The point is I don't want to be sitting here for 3 days waiting like i did the last time needlessly, if this is screwed up on their end or its possible for them to screw it up I want to contact them now.

[thecoalman]

Ok so I did a whois lookup on network-tools.com, here's snippet of the reults:

Domain Name: DOMAIN.NET
Registrar: Registrar
Whois Server: whois.hostingcompainesregistrar.com
Referral URL: http://www.hostingcompainesregistrar.com
Name Server: NS1.OLDNAMESERVER.COM
Name Server: NS2.OLDNAMESERVER.COM
Status: ok
Updated Date: 03-may-2007
Creation Date: 02-may-2003
Expiration Date: 02-may-2008

>>> Last update of whois database: Fri, 21 Mar 2008 17:09:19 UTC <<<

then down the bottom I get:

Domain servers in listed order:
ns1.mydomain.com
ns2.mydomain.com

That's not right correct?

[Ron]

There is ANOTHER screen on aletianic.com that you need to fill out. The change you made was from the domain control screen, where you told it to use ns1/ns2.yourdomain.com as the DNS server for the domain.

Now check the left-hand column for a link that says: "Register DNS"

That's where you enter the IP address(es) for your ns1/ns2.mydomain.com nameservers.

[EuroNut]

There are two stages to setting up your nameservers at a registry (Nothing to do with how you have them set on your VPS):

1) You need to register the hostnames of your nameservers and tell the registry what IP addresses they use.

2) You then need to edit the domain record that you want to use under those nameservers, and set it to use those 2 nameservers.

It's sounding very much like you've done 2 and not 1 above. So, whilst you're correctly seeing that yourdomain.com should use ns1 and ns2.yourdomain.com as it's nameservers, you have yet to tell the registry that ns1.yourdomain.com is on IP address xx.xx.xx.xx and that ns2.yourdomain.com is on IP address xx.xx.xx.xx

Depending which registrar you're with, look around their menus for somewhere to register nameservers, set up hostnames, or some similar terminology that lets you tell the world where the heck your nameservers are (ie: what their IPs are).

[Vin DSL]

Sorry! I only have a minute...

Here's a whois snippet for one of my sites:

Domain Name:LENON.INFO
Sponsoring Registrar:1&1 Internet AG
Whois Server: whois.afilias.info
Name Server:NS.LENON.INFO
Name Server:NS2.LENON.INFO
Status:OK
Created On:25-Dec-2004 17:41:13 UTC
Last Updated On:05-Oct-2007 05:39:19 UTC
Expiration Date:25-Dec-2008 17:41:13 UTC

And, another...

Domain Name: VINDSL.COM
Registrar: SCHLUND+PARTNER AG
Whois Server: whois.schlund.info
Referral URL: http://REGISTRAR.SCHLUND.INFO
Name Server: NS.VINDSL.COM
Name Server: NS2.VINDSL.COM
Name Server: NS3.VINDSL.COM
Status: ok
Updated Date: 24-sep-2007
Creation Date: 29-nov-2006
Expiration Date: 29-nov-2008

Apologies, if you already answered this, but why are you using 'NS1'

Never heard of that before!

Gotta run! BBL...

[thecoalman]

Thanks for the input, It's resolving correctly now. As I mentioned above there was a problem when I originally moved my own domain months ago which is why I had concerns with this one:

1) You need to register the hostnames of your nameservers and tell the registry what IP addresses they use.

Which is exactly why I think my domain wasn't resolving correctly a few months back, you can only add the nemaservers at the registar , there is no setting for adding IP'sI just wanted to make sure I wasn't sitting on my hands with this domain waiting for something to happen that wasn't.

This particular comapany has been nothing but nightmare for the last 6 months and I have absolutely no confidence in anything they do.

[thecoalman]

Apologies, if you already answered this, but why are you using 'NS1'

Never heard of that before!

Gotta run! BBL...

That's what it was set to when I purchased the VPS, I've seen it like that elsewhere in other whois queries. It's good enough for google so I guess its good enough for me.

[Ron]

...like 8 people saying the same thing over and over and over again...

[Vin DSL]

...like 8 people saying the same thing over and over and over again...

And, 3 ppl with not enough time to read through it...

[Gwaihir]

Which is exactly why I think my domain wasn't resolving correctly a few months back, you can only add the nemaservers at the registar , there is no setting for adding IP's [..]

This particular comapany has been nothing but nightmare for the last 6 months and I have absolutely no confidence in anything they do.

That's quite possible. There are registrars that do not offer facilities for registering name servers (step 1 as mentioned above). You'll have to find yourself a different registrar.

Apologies, if you already answered this, but why are you using 'NS1'

Why not? Both 'NS' and 'NS1' are perfectly normal names for them. JagPC even has ones labelled 'VNS1' and 'VNS2'. Assuming there is an RFC somewhere on which the common convention is based, I wonder if those are in it..

[Vin DSL]

Why not? Both 'NS' and 'NS1' are perfectly normal names for them.

You're right!

I was just reading through the various RFCs concerning DNS resolution, and that's a perfectly acceptable name.

It *seems* like, in the old days, all you could choose was NS or DNS, but now anything goes...