View Full Version : Propagation frustration
bellgamin
08-24-2002, 06:32 PM
Deal with this at leisure - it's not an urgent problem for reason you will see.
For simplicity I will use hypothetical names...
A) On 8/20/02...
1) I changed the DNS for domain1.org from oldhost1 to AOH.
2) On that same date I changed the DNS for domain2.org from oldhost2 to AOH.
B) Within just a few hours, AOH's DNS were shown for BOTH domains in...
http://www.betterwhois.com/
... & http://www.networksolutions.com/cgi-bin/whois/whois
C) On 8/21/02 I verified that domain1.org was being accessed from AOH's servers. It still is, as of today, 8/24. Ergo, all went well with domain1.org.
D) However, as of 8/24/02, on 3 different browsers, domain2.org tests out as still being accessed from oldhost2's servers, NOT AOH's. [FYI the way I check this is to have the index page for domain2 on oldhost2 be slightly different from the index page for domain2 on AOH.]
E) When I PING domain2.org, it gives me an AOH IP...
AlertSite - Test Results
Sat Aug 24 20:52:37 UCT
ping biblebell.org
PING biblebell.org (64.191.10.112) from 130.94.244.195 : 56(84) bytes of data.
64 bytes from 64.191.10.112: icmp_seq=0 ttl=240 time=53.128 msec
64 bytes from 64.191.10.112: icmp_seq=1 ttl=240 time=53.125 msec
64 bytes from 64.191.10.112: icmp_seq=2 ttl=240 time=53.066 msec
64 bytes from 64.191.10.112: icmp_seq=3 ttl=240 time=53.283 msec
64 bytes from 64.191.10.112: icmp_seq=4 ttl=240 time=53.090 msec
F) A traceroute also takes me to AOH...
1) 216.46.228.228 port-216-3073252-dal16509a-drtn.devices.datareturn.net
2) 64.29.192.4 port-64-1949700-dal16509b-drtn.devices.datareturn.net
3) 64.29.192.237 port-64-1949933-zzt0prespect.devices.datareturn.net
4) 64.29.192.226 port-64-1949922-zzt0prespect.devices.datareturn.net
5) 209.246.152.201 gigabitethernet3-0-101.ipcolo2.dallas1.level3.net
6) 209.244.15.93 gigabitethernet10-1.core2.dallas1.level3.net
7) 209.245.240.150 102.atm5-0.br1.dfw9.alter.net
8) 152.63.103.77 0.so-3-3-0.xl2.dfw9.alter.net
9) 152.63.2.181 0.so-0-0-0.tl2.dfw9.alter.net
10) 152.63.3.190 0.so-4-0-0.tl2.dca8.alter.net
11) 152.63.144.30 0.so-4-3-0.xl2.dca8.alter.net
12) 146.188.163.29 188.at-0-2-0.CL2.DCA1.ALTER.NET
13) 152.63.39.213 194.atm5-0.gw8.phl1.alter.net
14) 157.130.223.162 hostnoc-gw.customer.alter.net
15) 64.191.10.112
Trace complete
I realize that, IF this is a *problem* it is one for solution by me & my registrar, NOT AOH.
However, I'm not sure if I really do have a problem yet [I can & will continue updating domain2.org on oldhost2 until I verify FULL propagation]
So all I want is your comments and commiseration.
Bellgamin :confused:
admin
08-24-2002, 06:47 PM
This is certainly an interesting issue. Can you PM me or tell me here what the difference is in the 2 pages so I will know which one I am looking at?
I have verified that NS1, NS2 and NS3 all report the correct IP address for your domain.com and www.domain.com.
I would appreciate it if you would do the following 2 commands from your command prompt:
ping www.biblebell.org
ping biblebell.org
I realize you reported some of this, but it looks like the ping you reported was from a different site rather than your pc.
bellgamin
08-24-2002, 07:23 PM
A) Okay, the difference is...
oldhost [futurequest.net] index page shows Saturday's date in the top part
My index page for AOH shows Sunday
B) For convenience...
domain...
http://www.biblebell.org/
Temporary AOH link...
http://64.191.10.112/~boldar1/
C) Never thought of pinging from my own box. Results...
C:\WINDOWS>ping biblebell.org
Pinging biblebell.org [63.151.147.67] with 32 bytes of data:
Reply from 63.151.147.67: bytes=32 time=206ms TTL=51
Reply from 63.151.147.67: bytes=32 time=206ms TTL=51
Reply from 63.151.147.67: bytes=32 time=220ms TTL=51
Reply from 63.151.147.67: bytes=32 time=219ms TTL=51
Ping statistics for 63.151.147.67:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 206ms, Maximum = 220ms, Average = 212ms
D) Looks like you put your finger on the problem. Somewhere in my computer it is remembering biblebell.org's OLD IP.
Any idea where is this IP # lodged, so I can erase it? [I'm using WinMe]
admin
08-24-2002, 07:43 PM
Use the search function and do a search for a file named hosts. It is possible that the entry could be there...but you would have had to add it manually. If you could, go to a command prompt and type ipconfig /all and paste the results here..I will use the information you provide to see what results your ISP's dns is providing to determine if the problem is on your computer or on your ISP.
bellgamin
08-24-2002, 08:09 PM
I did the ipconfig/all. The screen zooms by real fast, & I don't know how to slow the buggah down, so here's the best I could do...
Windows IP Configuration
Host Name . . . . . . . . . : DEFAULT
DNS Servers . . . . . . . . : 64.75.176.66
64.75.176.12
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No
Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-01
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :
1 Ethernet adapter :
Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-00
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 64.75.153.214
Subnet Mask . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . : 64.75.153.214
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :
C:\WINDOWS>
admin
08-24-2002, 08:29 PM
I am not sure if the following is a valid command on ME, but go to a command prompt and see if nslookup works.
the command is
nslookup biblebell.org
nslookup www.biblebell.org
bellgamin
08-24-2002, 08:41 PM
Nope...
C:\WINDOWS>nslookup biblebell.org
Bad command or file name
C:\WINDOWS>nslookup www.biblebell.org
Bad command or file name
C:\WINDOWS>
Did you try to goto http://www.biblebell.org/ from your end? If you did, & if you got the AOH version, it pretty much has to be a problem at MY end, right?
PS I have other, unused domains in my pocket. They are sitting with my registrar, gandi.net, in Paris. They are all set to redirect to http://www.biblebell.org/
All of them still go to the futurequest version, not AOH's. For example...
http://www.christian-bible-studies.org/
http://www.cyber-chapel.net/
admin
08-24-2002, 10:32 PM
I tried all 3 url's that you posted. I get a date of sunday on all of them. I sent an email to your ISP to see if they could offer some ideas. I have not heard back from them.
bellgamin
08-24-2002, 10:54 PM
Wheesht! It looks like everyone in the world can access my domain on AOH except me. So... I'll just use another route until this situation gets worked out.
By the way, my ISP is in Hawaii & they are most definitely on Hawaiian time. Maybe [I say maybe] they will answer late Monday, if at all.
Danny, this has been fun for me [sort of], and I hope it wasn't a total headache for you. I'm gonna go play with my granddaughter Kiana [2 years 4 months].
Have a joyous week-end.
Shalom,
Bellgamin
admin
08-24-2002, 10:59 PM
Sorry you are having problems. I have seen similar issues with a customer of mine in UAE and his ISP was able to fix his problems as well. Hopefully your isp will be able to fix it for you.
bellgamin
08-25-2002, 06:22 AM
Whessht! Maybe it IS a propagation issue.
Saturday night I checked eMail. I got several messages telling me about new posts to various threads that I am following in this forum -- that is, AOH's forum.
All of those messages went <from> AOH <to> my website at my PRIOR host (futurequest).
Shown below is cut&paste of Calypso's logs for 10:56 PM Saturday. Note that the eMail was received from pop.biblebell.org -- the server at my old host. Moreover the login was by xbiblebell-biblebell <at> pop.biblebell.org, which is distinctly tied to my old host.
To wit...
*** Checking mail for account 'Biblebell' @ 08/24/2002 10:56 PM ***
Connecting to: 'pop.biblebell.org' -> Successful
Logging into POP3 account: 'xbiblebell-biblebell@pop.biblebell.org' -> Successful
Retrieving 1 of 11. -> Successful
Retrieving 2 of 11. -> Successful
Retrieving 3 of 11. -> Successful
Retrieving 4 of 11. -> Successful
Retrieving 5 of 11. -> Successful
Retrieving 6 of 11. -> Successful
Retrieving 7 of 11. -> Successful
Retrieving 8 of 11. -> Successful
Retrieving 9 of 11. -> Successful
Retrieving 10 of 11. -> Successful
Retrieving 11 of 11. -> Successful
Deleted message: "Reply to post 'Propagation frustration'"
Deleted message: "Reply to post 'How to configure ANOTHER email program'"
Deleted message: "Reply to post 'How to configure ANOTHER email program'"
Deleted message: "Reply to post 'How to configure ANOTHER email program'"
Deleted message: "Reply to post 'Propagation frustration'"
Deleted message: "Reply to post 'Dealing with Spam'"
Deleted message: "Reply to post 'How to configure ANOTHER email program'"
Deleted message: "Diary of a Bible"
Deleted message: "Reply to post 'Propagation frustration'"
Deleted message: "Reply to post 'Dealing with Spam'"
Deleted message: "Reply to post 'Propagation frustration'"
Logging out of POP3 account: 'xbiblebell-biblebell@pop.biblebell.org' -> Successful
Disconnecting -> Successful
So I am STILL getting biblebell eMail delivered to both my prior host (futurequest) & to my present host (AOH)!!
Could propagation be taking this bloody long? Or what, I wonder?
Regards,
Bellgamin
admin
08-25-2002, 09:42 AM
One thing that may also have an impact here is Futurequest's ttl. The ttl is the time to live value which specifies how long a dns server may hold this information. Futurequest chose a value of 71 hours for this value. The dns servers at our datacenter that we query from (not that we provide information from) still have 33 hours left.
FYI we use between 1 and 4 hour ttl values.
bellgamin
08-26-2002, 05:10 AM
I have forwarded this issue to my ISP, asking for resolution. I will advise you how it comes out.
Danny -- you IZZZZ the man! Your help is far & above what anyone can or should expect of any host.
But then... you're NOT just any host. I truly appreciate that fact.
Shalom & aloha,
Bellgamin
P.S. My wife advises you to keep a copy of these warm comments, so you will have them to send back to me when, one day, I go unreasonable & ballistic over some minor issue or the other.
Now why in the world would she say a thing like that, I wonder??? :D
Shalom & aloha,
Bellgamin
admin
08-26-2002, 09:11 AM
:D :D :D :D
admin
08-26-2002, 11:29 PM
Here is the reply I got back from your isp:
Aloha,
Your inquiry has been forwarded to our DNS admistrators for further
review. Regards, HOL Support.
bellgamin
08-27-2002, 05:45 AM
I verified that the problem was uniquely with my ISP. They didn't argue the point.
My ISP's tech spt [a real nice fellow named Pat] came up with the following...
Aloha Bill,
Looks like our modem pool service provider's DNS servers are hung up on
the expiration date from your old DNS servers. It looks like it will hang
for another 12 days. I will ask them to flush their DNS cache but I don't
think they will do it for a single domain. More tha likely they will tell
me to wait for the expiration to take place.
In the meantime you can add the following entry into your hosts file:
64.191.10.112 www.biblebell.org
64.191.10.112 mail.biblebell.org
I'll let you know if I hear anything else.
Cheers,
--pat
I added the suggested stuff into windows\hosts & also into windows\hosts.SAM. [What am SAM, I wonder???]
It worked gangbusters. Now I can EASILY access my site on AOH's servers. I could access it before, but not so easily.
Wow, AOH's servers are super-fast compared with oldhost -- & oldhost runs its own data center. Interesting, wot?
Regards, Bellgamin
~~~~~~~~
Stop winking at me. You're making me nervous.:p
admin
08-27-2002, 05:48 AM
Originally posted by bellgamin
~~~~~~~~
Stop winking at me. You're making me nervous.:p
;)
Afkamm
08-27-2002, 02:13 PM
Originally posted by bellgamin
I added the suggested stuff into windows\hosts & also into windows\hosts.SAM. [What am SAM, I wonder???]
SAM is short for the word sample. If you open the file in a text editor it'll say that :D
I have a HOST file that's filled with advert server addresses that all point to 127.0.0.1, so all I get are blank pages instead of pages full of adverts, want a copy?
Marc :O)
admin
08-27-2002, 03:11 PM
Well gosh thats a good idea...never thought of that
Good thinking.
Afkamm
08-27-2002, 03:17 PM
Don't thank me, got it from the KazaaLite website :D
The file's attached if you want to take a looky.
Marc :O)
bellgamin
08-27-2002, 03:48 PM
I took a look. Good schtick but I don't need such.
My browser [Opera] is structured to kill pop-ups/pop-unders, & all manner of evil.
My firewall [Outpost] is a splendid ad turner-offer. In fact, there is a *suthee cult* that specializes in constantly expanding OP's ferocity as an ad-killer. Here's a link to that cult's frequently updated list of raw, bleeding meat for OP to rip/tear/digest/excrete....
http://www.staff.uiuc.edu/~ehowes/resource.htm#Outpost
And oh... by the way, OP is also a great firewall.
Galumph,
Bellgamin
vBulletin® v3.7.3, Copyright ©2000-2008, Jelsoft Enterprises Ltd.