migrating website to new server, want to reduce TTL
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
migrating website to new server, want to reduce TTL
I'm tasked with migrating a website to a new dedicated server. To make this easier, I'd like to reduce the TTL for all DNS records associated with this site so I can make the switch quickly when the time comes. I'm confused about who to contact.
The domain is registered through godaddy and I see that the name servers specified in that account to dns1.nettica.com, dns2.nettica.com, etc. I get inconsistent results from dig. Sometimes the TTL values are about 3600 seconds:
Code:
[root@server] ~ >> dig mybookstoreandmore.com any
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> mybookstoreandmore.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57455
;; flags: qr rd ra; QUERY: 1, ANSWER: 12, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;mybookstoreandmore.com. IN ANY
;; ANSWER SECTION:
mybookstoreandmore.com. 3423 IN MX 20 aspmx3.googlemail.com.
mybookstoreandmore.com. 3423 IN MX 5 aspmx.1.google.com.
mybookstoreandmore.com. 3423 IN MX 10 alt1.aspmx.1.google.com.
mybookstoreandmore.com. 3423 IN MX 10 alt2.aspmx.1.google.com.
mybookstoreandmore.com. 3423 IN MX 20 aspmx2.googlemail.com.
mybookstoreandmore.com. 3423 IN SOA dns1.nettica.com. hostmaster.nettica.com. 35 7200 600 604800 3600
mybookstoreandmore.com. 3171 IN A 74.54.212.133
mybookstoreandmore.com. 3423 IN NS dns3.nettica.com.
mybookstoreandmore.com. 3423 IN NS dns1.nettica.com.
mybookstoreandmore.com. 3423 IN NS dns4.nettica.com.
mybookstoreandmore.com. 3423 IN NS dns2.nettica.com.
mybookstoreandmore.com. 3423 IN NS dns5.nettica.com.
;; Query time: 1 msec
;; SERVER: 69.16.234.115#53(69.16.234.115)
;; WHEN: Mon Mar 8 17:11:14 2010
;; MSG SIZE rcvd: 336
sometimes they are 180000 seconds:
Code:
[root@server] ~ >> dig mybookstoreandmore.com any
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> mybookstoreandmore.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36518
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;mybookstoreandmore.com. IN ANY
;; ANSWER SECTION:
mybookstoreandmore.com. 172439 IN NS dns1.nettica.com.
mybookstoreandmore.com. 172439 IN NS dns2.nettica.com.
mybookstoreandmore.com. 172439 IN NS dns3.nettica.com.
mybookstoreandmore.com. 172439 IN NS dns4.nettica.com.
mybookstoreandmore.com. 172439 IN NS dns5.nettica.com.
;; Query time: 0 msec
;; SERVER: 69.16.234.115#53(69.16.234.115)
;; WHEN: Mon Mar 8 17:11:39 2010
;; MSG SIZE rcvd: 143
Lord knows I'd hate to wait around for 50 hours for the move to go through. Should I contact godaddy and ask for shorter TTL values? Is there any point in contacting nettica and ask for shorter ttl values?
core:~$ whois mybookstoreandmore.com
Whois Server Version 2.0
Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.
Domain Name: MYBOOKSTOREANDMORE.COM
Registrar: GODADDY.COM, INC.
Whois Server: whois.godaddy.com
Referral URL: http://registrar.godaddy.com
Name Server: DNS1.NETTICA.COM
Name Server: DNS2.NETTICA.COM
Name Server: DNS3.NETTICA.COM
Name Server: DNS4.NETTICA.COM
Name Server: DNS5.NETTICA.COM
Status: clientDeleteProhibited
Status: clientRenewProhibited
Status: clientTransferProhibited
Status: clientUpdateProhibited
Updated Date: 04-jan-2010
Creation Date: 06-sep-2005
Expiration Date: 06-sep-2016
>>> Last update of whois database: Mon, 08 Mar 2010 22:33:11 UTC <<<
NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.
TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.
The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.The data contained in GoDaddy.com, Inc.'s WhoIs database,
while believed by the company to be reliable, is provided "as is"
with no guarantee or warranties regarding its accuracy. This
information is provided for the sole purpose of assisting you
in obtaining information about domain name registration records.
Any use of this data for any other purpose is expressly forbidden without the prior written
permission of GoDaddy.com, Inc. By submitting an inquiry,
you agree to these terms of usage and limitations of warranty. In particular,
you agree not to use this data to allow, enable, or otherwise make possible,
dissemination or collection of this data, in part or in its entirety, for any
purpose, such as the transmission of unsolicited advertising and
and solicitations of any kind, including spam. You further agree
not to use this data to enable high volume, automated or robotic electronic
processes designed to collect or compile this data for any purpose,
including mining this data for your own personal or commercial purposes.
Please note: the registrant of the domain name is specified
in the "registrant" field. In most cases, GoDaddy.com, Inc.
is not the registrant of domain names listed in this database.
Registrant:
Christina Brashear
577 Mulberry Street
Suite 1520
Macon, Georgia 31201
United States
Registered through: GoDaddy.com, Inc. (http://www.godaddy.com)
Domain Name: MYBOOKSTOREANDMORE.COM
Created on: 06-Sep-05
Expires on: 06-Sep-16
Last Updated on: 11-Apr-08
Administrative Contact:
Brashear, Christina crissyb65@gmail.com
577 Mulberry Street
Suite 1520
Macon, Georgia 31201
United States
+1.4783145144 Fax -- +1.4783145148
Technical Contact:
Brashear, Christina crissyb65@gmail.com
577 Mulberry Street
Suite 1520
Macon, Georgia 31201
United States
+1.4783145144 Fax -- +1.4783145148
Domain servers in listed order:
DNS1.NETTICA.COM
DNS2.NETTICA.COM
DNS3.NETTICA.COM
DNS4.NETTICA.COM
DNS5.NETTICA.COM
You would need to contact nettica to update your dns ttl. Godaddy can host your dns, I have a few person domains that use them and it's nice to have everything in one place as far as registrar and dns goes if you're not going to have enough servers running to provide redundant dns on separate networks.
I'm having a really hard time understanding why I get such radically different TTL values depending which server I check this from. I ran the command dig mybookstoreandmore.com ns on various machines and get different ttls:
my mac:
Code:
; <<>> DiG 9.4.3-P3 <<>> mybookstoreandmore.com ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22812
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;mybookstoreandmore.com. IN NS
;; ANSWER SECTION:
mybookstoreandmore.com. 3600 IN NS dns1.nettica.com.
mybookstoreandmore.com. 3600 IN NS dns3.nettica.com.
mybookstoreandmore.com. 3600 IN NS dns2.nettica.com.
mybookstoreandmore.com. 3600 IN NS dns4.nettica.com.
mybookstoreandmore.com. 3600 IN NS dns5.nettica.com.
;; Query time: 202 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Mon Mar 8 15:59:43 2010
;; MSG SIZE rcvd: 143
the new server, a centOS machine:
Code:
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> mybookstoreandmore.com ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27643
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;mybookstoreandmore.com. IN NS
;; ANSWER SECTION:
mybookstoreandmore.com. 165842 IN NS dns1.nettica.com.
mybookstoreandmore.com. 165842 IN NS dns2.nettica.com.
mybookstoreandmore.com. 165842 IN NS dns3.nettica.com.
mybookstoreandmore.com. 165842 IN NS dns4.nettica.com.
mybookstoreandmore.com. 165842 IN NS dns5.nettica.com.
;; Query time: 0 msec
;; SERVER: 69.16.234.115#53(69.16.234.115)
;; WHEN: Mon Mar 8 18:59:29 2010
;; MSG SIZE rcvd: 143
a debian box in arkansas:
Code:
; <<>> DiG 9.5.1-P3 <<>> mybookstoreandmore.com ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56660
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 5
;; QUESTION SECTION:
;mybookstoreandmore.com. IN NS
;; ANSWER SECTION:
mybookstoreandmore.com. 84976 IN NS dns5.nettica.com.
mybookstoreandmore.com. 84976 IN NS dns3.nettica.com.
mybookstoreandmore.com. 84976 IN NS dns4.nettica.com.
mybookstoreandmore.com. 84976 IN NS dns1.nettica.com.
mybookstoreandmore.com. 84976 IN NS dns2.nettica.com.
;; ADDITIONAL SECTION:
dns1.nettica.com. 5978 IN A 64.94.136.11
dns2.nettica.com. 5299 IN A 64.237.45.34
dns3.nettica.com. 17240 IN A 64.94.136.13
dns4.nettica.com. 8633 IN A 69.41.170.223
dns5.nettica.com. 1403 IN A 212.100.247.15
;; Query time: 0 msec
;; SERVER: 67.14.192.2#53(67.14.192.2)
;; WHEN: Mon Mar 8 18:01:19 2010
;; MSG SIZE rcvd: 223
When I do dig mybookstoreandmore.com ns @dns1.nettica.com then the results are all the same, with TTL of 3600:
Code:
; <<>> DiG 9.5.1-P3 <<>> mybookstoreandmore.com ns @dns1.nettica.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60776
;; flags: qr aa rd; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 5
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;mybookstoreandmore.com. IN NS
;; ANSWER SECTION:
mybookstoreandmore.com. 3600 IN NS dns2.nettica.com.
mybookstoreandmore.com. 3600 IN NS dns3.nettica.com.
mybookstoreandmore.com. 3600 IN NS dns4.nettica.com.
mybookstoreandmore.com. 3600 IN NS dns5.nettica.com.
mybookstoreandmore.com. 3600 IN NS dns1.nettica.com.
;; ADDITIONAL SECTION:
dns2.nettica.com. 21600 IN A 64.237.45.34
dns3.nettica.com. 21600 IN A 64.94.136.13
dns4.nettica.com. 21600 IN A 69.41.170.223
dns5.nettica.com. 21600 IN A 212.100.247.15
dns1.nettica.com. 21600 IN A 64.94.136.11
;; Query time: 84 msec
;; SERVER: 64.94.136.11#53(64.94.136.11)
;; WHEN: Mon Mar 8 18:02:42 2010
;; MSG SIZE rcvd: 223
All you need to know is that if GoDaddy is going to be the new DNS host then:
1. stage the zone file within the GoDaddy DNS control panel. contact nettica about sending you a copy of the current zone file for mybookstoreandmore.com
2. Once the zone file is prepped on the GoDaddy end then adjust the TTL to something like 60 and then cut over from nettica to GoDaddy
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.