jersey needs ip

[Crock]

optimum online > comcast

 

[Kooldino]

@ Roni - Lame excuse.

 

[Orthonormal]

How long has the problem been going on? It takes a few days for IP address changes to propagate across the internet. Some nameservers will update almost immediately, while others might take a couple hours or a couple days.

 

[jersey_emt]

How long has the problem been going on? It takes a few days for IP address changes to propagate across the internet. Some nameservers will update almost immediately, while others might take a couple hours or a couple days.

I've never seen a domain take more than 24 hours to propagate.

It's been since Sunday. 96 hours.

 

[enry]

My zonefiles have a fairly long TTL, BUT, that only applies for records that CHANGED... what I did, was forward all requests from the old site to www2, which is a NEW record, and should be here without problem. It happened a while back that a bunch of people couldn't reach the site, and that was regardless of changes or updates we did....

I would also like someone from EV1 to look into this....

 

[KpaBap]

use the sbcglobal/pacbell/whateverthehell dns servers instead of comcast's

206.13,28.12
206.13.31.12

might not give you the best speeds since they're over here on the west coast but they're wide open

 

[#878MSPChick]

I am so thankful for this post. I cannot get on from work anymore, so I am going to try to fix it with the info I have learned here. Thanks again.

 

[roni]

@ Roni - Lame excuse.

yeah, well i was on http://www.mazdamp3.com on sunday night. where were you?

 

[enigM@]

finally!! haha it works now using that method

 

[protegeV]

Myself and Derrick had the same problem almost a month ago. The host file thing fixed it thanks to fkmp5(franks)

 

[Mr. Win]

I am so thankful for this post. I cannot get on from work anymore, so I am going to try to fix it with the info I have learned here. Thanks again.

ummm i hope you dont work at a large office... they dont like this...

 

[Kooldino]

yeah, well i was on http://www.mazdamp3.com on sunday night. where were you?

Hey, I could still get to it from my pimp daddy cell phone.

 

[BlueMonsta]

proxy = the best temp workaround

that help desk tech. didnt really help... lol
Its not my problems blah blah, i'd go complain on his sorry ass

 

[SoonP5ismine]

I've never seen a domain take more than 24 hours to propagate.

It's been since Sunday. 96 hours.

I work at comcast and i work in your area and i know where you live LOL. dont worry im not going to go steal your car or break in to your house LOL. you will probably have to enter this dns server address into your router config/windows manual dns settings 68.39.224.7. you are probably using the 68.39.224.5 and 68.39.224.6 right now if you havent modified any of your network settings. 68.39.224.7 is a dns server that is not listed/known by most of all people working in comcast. this server is supposed to be the fastest one for this area since not too many people know about it. and its kinda like a backup of the other 2 servers.

I am able to connect to this site with no problems using that dns server. i havent tried it with the default ones since im using the 68.39.224.7 server for many months now with no problems.

If you have a problem still and dont know how to edit your network dns settings then pm me and maybe i can walk you thru it on the phone.

 

[jersey_emt]

I work at comcast and i work in your area and i know where you live LOL. dont worry im not going to go steal your car or break in to your house LOL. you will probably have to enter this dns server address into your router config/windows manual dns settings 68.39.224.7. you are probably using the 68.39.224.5 and 68.39.224.6 right now if you havent modified any of your network settings. 68.39.224.7 is a dns server that is not listed/known by most of all people working in comcast. this server is supposed to be the fastest one for this area since not too many people know about it. and its kinda like a backup of the other 2 servers.

I am able to connect to this site with no problems using that dns server. i havent tried it with the default ones since im using the 68.39.224.7 server for many months now with no problems.

If you have a problem still and dont know how to edit your network dns settings then pm me and maybe i can walk you thru it on the phone.

Sweet dude! Thanks so much. I'd much rather use a better (and faster) DNS server than make a stupid hack in the windows hosts file.

 

[KyRaceFan]

Sorry, didnt read much of the thread, but if its a TRUE DNS issue, then specfify 4.2.2.1 in the DNS server setting of tcp/ip.

Ive worked in Internet Help Desk for 2+ years, and DNS servers crash from time to time, it could also be the route it takes. Once its pasts comcasts gateway and DNS, theres not a whole lot they can do, since its a backbone routing issue.

If you need more info on specifying an IP, let me know.

 

[elias1974]

u can easily use DNS of another ISP...
If you have a router, and a private address behind the router like 192.168.1.x
you can change the local TCP/IP settings and enter the DNS of another ISP like optimum or road runner...

 

[r1ceburner]

For those of you who are having DNS issues, below are a few internet reachable DNS servers that you can use as fast alternate servers, in-case yours is hosed.

151.164.1.8 - SBC Primary DNS
151.164.1.7 - SBC Secondary DNS
138.237.128.3 - Texas Christian University DNS (Go Frogs!)
4.2.2.1 - Verizon Primary DNS
4.2.2.2 - Verizon Secondary DNS
4.2.2.3 - Verizon DSL DNS
4.2.2.4 - VerizonWireless DNS (VZW service)