| Author | Thread |
|
|
04/07/2005 11:11:43 PM · #1 |
I'm having DNS name resolution issues. Can someone get me the IP address for the following servers?
//www.google.com
//www.zoneedit.com
//www.hawkins.nu
Thanks,
Terry
|
|
|
|
04/07/2005 11:17:55 PM · #2 |
google: 64.233.161.104
zoneedit: 69.72.176.180
hawkins: 65.82.11.69 |
|
|
|
04/07/2005 11:21:43 PM · #3 |
I am getting...
216.239.39.99 for Google.com
and
69.72.176.188 for zoneedit.com
Hawkins.nu agrees with what John got.
|
|
|
|
04/07/2005 11:30:31 PM · #4 |
Im getting:
Google: 64.233.187.99
Zoneedit: 69.72.176.188
hawkins: 65.82.11.69
How are you going about getting the IP addresses?
Use 'tracert' in the command prompt if you have not tried that. I will give you a trail of how you get to there server from your card to them. It will also show the IP address it is looking for first.
Message edited by author 2005-04-07 23:33:11. |
|
|
|
04/07/2005 11:33:03 PM · #5 |
Thanks guys. The differences are due to load-balancing and mirroring.
I need two more: //www.kloth.net and www.comcast.com.
Thanks,
Terry
Message edited by author 2005-04-07 23:34:12.
|
|
|
|
04/07/2005 11:34:05 PM · #6 |
Originally posted by ClubJuggle:
Thanks guys. The differences are due to load-balancing and mirroring.
I need one more: //www.kloth.net.
Thanks,
Terry |
kloth: 213.133.98.149 |
|
|
|
04/07/2005 11:35:56 PM · #7 |
|
|
|
04/07/2005 11:36:30 PM · #8 |
comcast.com = 164.109.28.3
|
|
|
|
04/07/2005 11:49:16 PM · #9 |
NSLOOKUP returns
Non-authoritative answer:
Name: google.com
Addresses: 216.239.39.99, 216.239.57.99, 216.239.37.99
Non-authoritative answer:
Name: comcast.com
Address: 164.109.28.3
Non-authoritative answer:
Name: kloth.net
Address: 213.133.98.149
Non-authoritative answer:
Name: zoneedit.com
Addresses: 69.72.176.188, 69.72.176.180
Non-authoritative answer:
Name: hawkins.nu
Address: 65.82.11.69
|
|
|
|
04/08/2005 12:22:33 AM · #10 |
|
|
|
04/08/2005 12:26:57 AM · #11 |
Originally posted by deapee:
comcast has problems. |
Yes, here too. |
|
|
|
04/08/2005 01:11:57 AM · #12 |
| Good to know it wasn't just me. :) |
|
|
|
04/08/2005 01:14:22 AM · #13 |
| Anyone else had trouble with Verizon DSL lately? |
|
|
|
04/08/2005 01:16:57 AM · #14 |
Originally posted by kearock:
Anyone else had trouble with Verizon DSL lately? |
What kind of problem are you having? |
|
|
|
04/08/2005 01:21:09 AM · #15 |
| There have been some DNS Poisoning issues over the last few days that are pretty wide spread. Details here: //searchsecurity.techtarget.com/originalContent/0,289142,sid14_gci1076546,00.html |
|
|
|
04/08/2005 01:27:01 AM · #16 |
Originally posted by SDW65:
Originally posted by kearock:
Anyone else had trouble with Verizon DSL lately? |
What kind of problem are you having? |
It's been extremely slow and spotty in the past week. It's normally super fast. I'm told DSL degrades over distance, so since we live about 50 feet from the local Verizon building we get really good service normally - as good as it gets. But lately, you have to sit and wait while pages load or sometimes they don't load at all. |
|
|
|
04/08/2005 02:14:37 AM · #17 |
Originally posted by mk:
Originally posted by deapee:
comcast has problems. |
Yes, here too. |
Comcast had a national outage this evening. I'm not sure what the problem was. It was DNS certainly (since I could browse DPChallenge and some other sites fine by IP address, but not at all by name). Normally I would circumvent this by manually setting my computer to use non-Comcast name servers, but even that didn't help. I'm guessing that they were doing some filtering of port 53 at the perimiter while they nailed down the problem -- either that or a DNS poisoning attack was originating from within Comcast, and the requests were being blocked by Comcast's upstream provider(s).
-Terry
|
|
Home -
Challenges -
Community -
League -
Photos -
Cameras -
Lenses -
Learn -
Help -
Terms of Use -
Privacy -
Top ^
DPChallenge, and website content and design, Copyright © 2001-2026 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Current Server Time: 01/02/2026 07:37:51 AM EST.
