FQuest Notice: (DNS) Name Server IP addresses changed

[Terra]

Please make note that our new DNS IP addresses are now in effect:

Internic is now showing the HOST addresses proper, in both the root name servers, and also the whois listing (a miracle)...

7/10/00 (and prior):
ns1.FutureQuest.net 208.243.19.2
ns2.FutureQuest.net 208.243.19.3
ns3.FutureQuest.net 208.243.19.4

7/11/00 - 8/8/00
ns1.FutureQuest.net 208.243.19.2
ns2.FutureQuest.net 63.95.220.68
ns3.FutureQuest.net 208.243.19.4

8/9/00 onward
ns1.FutureQuest.net 63.95.221.2
ns2.FutureQuest.net 63.95.220.68
ns3.FutureQuest.net 63.144.24.2

10/2000 onward
ns1.FutureQuest.net 63.95.221.2
ns2.FutureQuest.net 63.151.112.2
ns3.FutureQuest.net 63.144.24.2

8/24/2001 onward
ns1.FutureQuest.net 63.151.147.2
ns2.FutureQuest.net 63.151.112.2
ns3.FutureQuest.net 63.144.24.2

9/28/2001 onward
ns1.FutureQuest.net 63.151.147.2
ns2.FutureQuest.net 209.116.212.2
ns3.FutureQuest.net 63.144.24.2

This change was done for 3 primary reasons:
1) Improve our redundancy and load balancing by shifting DNS servers to separate subnets.
2) Remove the strict restrictions that site owners were encountering registering certain International domain names (like .de and .ke)...[nbsp][nbsp]Namely RFC2182 in regards to same subnet...
3) Begin preparations for accelerated propagation

If you are registering new domain names, then your Registrar should gleem our DNS info straight from the root name-servers...[nbsp][nbsp]If they don't, and show old information - then see if you can update the form entries manually...[nbsp][nbsp]I've seen a major one *cough*joker*cough* use stale information and required an email (and few days wait) before it was all updated...

This is another major improvement in our service offerings that are starting to come down the pike...[nbsp][nbsp]We have been working for a very long time to make all of this (and to be seen) a reality, like the QuestAffiliates program...[nbsp][nbsp]Overall, you asked - and now we are delivering, with voracity, on our commitments...

--
Terra
--Still trying to perfect the 'One size fits all' concept--
FutureQuest

Edit by Bob - Updated Name Server IP Information

[JoeRT]

I'm still showing all the domains I've registered through different CORE registrars as having the old DNS info on NS1 and NS3, not just the ones I registered through *cough*joker*cough*.[nbsp][nbsp]So is this as much a *cough*joker*cough* issue as a CORE database issue?

I'm only showing NS2 has changed on my CORE registered domains.[nbsp][nbsp]If everyone at FQ that registered through a CORE registrar has only had NS2 changed, is this going to cause a problem at FQ?

-----------------------
Joe Torsitano
www.weatherforyou.com (http://www.weatherforyou.com)
www.tiswest.com (http://www.tiswest.com)
[nbsp][nbsp]-- Don't be makin' fun of my Joker[nbsp][nbsp](huh?)

[Terra]

When you fill out the forms, pay special attention to the email they send (if any)...[nbsp][nbsp]Many times that email is updated, whereas the online web form is not...

For verification, 2 ways to see:
1)
$dig @a.root-servers.net ns1.futurequest.net
$dig @a.root-servers.net ns2.futurequest.net
$dig @a.root-servers.net ns3.futurequest.net

The root servers *are* the authorative source and update way before the whois databases.

2)
$whois 'futurequest.net@whois.networksolutions.com'

This will also show the updates are in place...

Outside of that, the other registrars must have facilities in place to keep their information sychronized...[nbsp][nbsp]If they are not, then it is fallacy and I would shoot an email to them letting them know you are more cluefull then they... ;)

I don't forsee any major problems, and that is the whole reason I staggered the changes with 'NS2' being done first and 'NS1' and 'NS3' held off...

Right now I am seeing most traffic shifting over to the new name servers, plus I had low one hour TTL's on the old ones to further accelerate the crossover...

--
Terra
--Minimizing monkey wrenches--
FutureQuest

[JohnD]

So those of us who register directly with Network Solutions, etc., should put in a modify DNS request to them?

------------------
John Dunn
Algorithmic Arts
http://algoart.com

[Terra]

I am unsure as to why Network Solutions still requires the IP address for DNS servers...

Even if you were to fill out a new registration today, and use the old IP addresses - when you receive your Confirmation email you will find that it has automatically been updated...

My alert was only a heads up in case you encounter any problems...[nbsp][nbsp]When NS2 changed, _only_ Joker had a problem with registration which required me to send an email to them...[nbsp][nbsp]They assured me that when I dropped the hammer on NS1 and NS3, they would not get "stuck" again...

--
Terra
--It's not the computers, but rather the programmers--
FutureQuest

[JohnD]

I'm not an expert at this stuff, I just wanna keep my web site working.[nbsp][nbsp]The part of the Network Solutions form I have to change when I change ISP's looks like this:

>>Prime Name Server
>>7a. Primary Server Hostname.........: ns1.FutureQuest.net
>>7b. Primary Server Netaddress.......: 208.243.19.2
>>
>>Secondary Name Server(s)
>>8a. Secondary Server Hostname.......: ns2.FutureQuest.net
>>8b. Secondary Server Netaddress.....: 63.95.220.68
>>

My question is, do I submit another change to them, as if I was changing ISPs, so they will update whatever needs to be updated?

Please answer with one of the following:

Yes.
No.
Doesn't matter, but it wouldn't hurt.

Thanks,

------------------
John Dunn
Algorithmic Arts
http://algoart.com

[Terra]

My question is, do I submit another change to them, as if I was changing ISPs no

they will update whatever needs to be updated? yes (transparently)

--
Terra
--Hedging my bets--
FutureQuest

[JoeRT]

Wasn't the deadline August 9?[nbsp][nbsp]The domains I registered through any CORE registrar (not just Joker) still say:

ns1.futurequest.net 208.243.19.2
ns2.futurequest.net 63.95.220.68
ns3.futurequest.net 208.243.19.4

Are we who registered through CORE headed for a problem?

---------------------------
Joe Torsitano
www.weatherforyou.com (http://www.weatherforyou.com)
www.tiswest.com (http://www.tiswest.com)

[Terra]

I don't believe that it will be a problem...

Let me simplify sorta how it works, in perl:

print "$root_name_servers{'ns1.futurequest.net'}\n";

will return:
63.95.221.2

In the end, 'ns1.futurequest.net' is a lookup key for the real IP address...[nbsp][nbsp]Why registrars are still wanting IP numbers for DNS server addresses is beyond me as they should consult the 'root' name servers which control all of the steering...

--
Terra
--Sometimes I make things too complicated--
FutureQuest