Search Again:

Re: Help! I''m a newbie...

From: Sean Stephens
Date: Wednesday, May 2, 2001
Time: 2:32:08 pm

Thanks andrew and chris, you are magnificent

Still confused on some things though (I've set it all up and filled out the
network solutions form to change my nameservers IP address and hopefully it
will all come out in the wash)

Question: my old QDNS (and the examples in the QDNS manual) have servers
called ns1.xxx.com, whereas my new one contains my new IP address. What I
mean is, when you attach to a server using the remote manager software, the
"server" in the zone view or server view is an IP address and NOT in the
form of my name server. Does this matter? How do I change it if not?

I assume that it will work as long as I have the "master server" box with a
reference to the ns1.xxx.com under each record.

Then, (if I understand it), this is the way it will work (correct me if I am
wrong)...

1) Some guy types in "www.xxx.com"
2) His dial up account searches for "xxx.com" at one of the big 13 servers,
and is told to go to my server IP address.
3) QDNS gets the request and tells him to look under the record for
"xxx.com" where it finds another A record called "www.xxx.com" and tells him
it is on the IP address (actually on the same computer)
4) The server serves him the site.

Where does the reverse PTR lookup come in? Does it even matter?

Also, do I need to go to network solutions and change every single URL to
point at my name server? Or simply changing my nameserver's IP fixes them
all for me?

Thanks for the help

Sean





> From: "andrew" <andrew@ardentmicro.com>
> Organization: ardent micro
> Reply-To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
> Date: Wed, 2 May 2001 16:29:53 -0400
> To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
> Subject: Re: Help! I'm a newbie...
>
>> Is there any tried and true method of knowing exactly when this will
> switch
>> over so that I know everything is working from the moment the IP switch
>> happens on Network Solutions? How do I know when it has happened?
>
> No, because routers, proxy servers and other switching equipment around the
> internet "cache" (store) the IP addresses of webservers so they don't have
> to ask your nameserver "where" the webserver is every time someone types
> "xyz.com" into their browser.
>
> You can tell these machines not to remember this information and ask you
> more frequently, which is a good idea to do about 2 weeks before you switch
> the IPs over, but not every machine will obey your wishes. You do this by
> adjusting the "TTL" value (time to live) in the domain information (either
> for a specific machine address or for the domain as a whole). Setting a
> lower value forces (or at least tries to force) the other machine caching
> your information to re-query your nameserver more frequently.
>
> You only want to set lower TTL values before moving the site or server, and
> then return them to their default values afterwards, or your DNS will become
> bogged down answering "where are you" queries all day long.
>
> The default TTL for a domain is 86400 seconds (one day). You can reduce this
> to 14000 (four hours) a week before you move the DNS and webserver, and then
> there will be minimal interruption in your service. In my experience there's
> a lot of "bad" proxies and cache servers that ignore TTL settings take that
> long to refresh their cache.
>
>> P.S. What is a BIND?
>
> BIND (Berkeley Internet Name Domain) is a methodology by which domains are
> defined. There is a BIND Server that's freely distributed but only runs on
> UNIX or NT in emulation, but QuickDNS is world's easier to configure. If you
> want to step backwards 10 years (or a millenium in internet-time) go to
> http://www.isc.org/products/BIND/ and start reading about it.
>




Messages In This Thread:



Return to Digital Point Solutions' Home Page