Goddamn Network Solutions anyway

So for the past week, many people (but not everyone) have been unable to surf to my business Web site, obsidianfields.com. This means, among other things, that images posted in my LiveJournal are not appearing for everyone.

The site’s DNS records are correct, but for some reason, about a week ago Network Solutions’ WHOIS data started showing the wrong IP address for the site. I have no idea how or why; the name server information is right, but the IP address isn’t.

Network Solutions insists that there’s no problem on their end; there’s no way their database can be wrong; the problem must exist with the Web host, GoDaddy. Yet I can log on to the GoDaddy control panel, and GoDaddy’s name servers are showing the correct information. In fact, I can surf to the web site through a proxy server such as MegaProxy, and DNSStuff shows the correct information. It’s only Network Solutions that’s showing it wrong.

So if you guys can do me a great big favor, I’d really appreciate it. Go to

http://www.obsidianfields.com

and tell me what you see. If you can tell me who your ISP is, that’d really be helpful, too.

For all you geeks on my f’list, if the domain won’t come up for you, I’d appreciate if you can do a whois and tell me what’s showing as the site’s IP address and what name servers are listed as well.

44 thoughts on “Goddamn Network Solutions anyway

  1. Re: Obsidian Fields

    Looks like it comes through fine here. I’m going through Speakeasy.

    The first paragraph looks like:

    Obsidian Fields offers a complete range of services for the graphic arts industry, including consulting, pre-press, training, and design for print and Web. We offer computer services for Macintosh, Windows, and Unix-based clients.

  2. Re: Obsidian Fields

    Looks like it comes through fine here. I’m going through Speakeasy.

    The first paragraph looks like:

    Obsidian Fields offers a complete range of services for the graphic arts industry, including consulting, pre-press, training, and design for print and Web. We offer computer services for Macintosh, Windows, and Unix-based clients.

  3. Sprint, southwestern VA. I get the consulting page. On the unrelated weirdness side, though — all the whois servers I’ve tried today are refusing the connection. I’ve tried from three remote servers, too :/

  4. Sprint, southwestern VA. I get the consulting page. On the unrelated weirdness side, though — all the whois servers I’ve tried today are refusing the connection. I’ve tried from three remote servers, too :/

  5. Domain Name: OBSIDIANFIELDS.COM
    Registrar: NETWORK SOLUTIONS, LLC.
    Whois Server: whois.networksolutions.com
    Referral URL: http://www.networksolutions.com
    Name Server: WSC1.JOMAX.NET
    Name Server: WSC2.JOMAX.NET
    Status: ACTIVE
    Updated Date: 28-dec-2005
    Creation Date: 03-oct-1999
    Expiration Date: 03-oct-2006

    Aratinga:~ redjen$ host http://www.obsidianfields.com
    http://www.obsidianfields.com is an alias for obsidianfields.com.
    obsidianfields.com has address 64.202.163.7

    • obsidianfields.com has address 64.202.163.7

      Yep, that’s correct. For some reason, Network Solutions and some ISPs (apparently, ISPs affiliated with Time Warner) up and decided a few days back that the site’s IP address was a 219.something address, which is not even close to being right.

      Right now, Time Warner is showing the correct IP address, but Network Solutions’ WHOIS information now shows the site’s IP as 1.1.1.1…weird, huh?

  6. Domain Name: OBSIDIANFIELDS.COM
    Registrar: NETWORK SOLUTIONS, LLC.
    Whois Server: whois.networksolutions.com
    Referral URL: http://www.networksolutions.com
    Name Server: WSC1.JOMAX.NET
    Name Server: WSC2.JOMAX.NET
    Status: ACTIVE
    Updated Date: 28-dec-2005
    Creation Date: 03-oct-1999
    Expiration Date: 03-oct-2006

    Aratinga:~ redjen$ host http://www.obsidianfields.com
    http://www.obsidianfields.com is an alias for obsidianfields.com.
    obsidianfields.com has address 64.202.163.7

  7. Yesterday and earlier today I was unable to go to resolve dns for any of my websites from work, but other people were able to do such. I thought it was just a problem with the work network, but it might have been a more general DNS issue?

    • Good question. Who’s your work service provider? (Anyone in the Time Warner network, by any chance?)

      It appears the problem with my Web site was a corruption in the DNS records at Network Solutions. I pointed the name servers at a bogus address, then back at the GoDaddy name servers, which forced a refresh of the record, and lo and behold, this afternoon the site started resolving for me again. It seems that it affected only people using RoadRunner/Bright House/AO/et al, so I’m wondering if they also grabbed a corrupt name server record.

      Now what’s weird is that nobody else showed the incorrect IP address, and it seems nobody else had problems. *shrug* Weird.

  8. Yesterday and earlier today I was unable to go to resolve dns for any of my websites from work, but other people were able to do such. I thought it was just a problem with the work network, but it might have been a more general DNS issue?

  9. Works fine / Zen UK

    Works fine from Zen UK (www.zen.co.uk).

    The only thing I can imagine is that there is a problem somewhere – such as a honest mistake somewhere, or someone attempting to do a malicious take-over.

    Either way, in the interim, make sure that the domain is registrar locked (not sure if Network Solutions supports it, but they suck, and you should really consider moving to another service. I find Moniker (www.moniker.com) to be great for domain management. Finally, in the DNS setup, set the name server to a shorter refresh time – perhaps 30 minutes or so – for a while. It means that it gets refreshed faster, and with some luck the problems go away faster. Not a solution, but it may kill off some of the symptoms faster whilst you find a decent solution.

    Godspeed, fella, and happy newyear 🙂

    Haje

    • Re: Works fine / Zen UK

      I’m in the process of transferring the registration from Network Solutions (may they rot in hell, or a place like hell), as this kind of issue has happened before. It definitely appears to have been a Network Solutions issue, though it’s working correctly now.

  10. Works fine / Zen UK

    Works fine from Zen UK (www.zen.co.uk).

    The only thing I can imagine is that there is a problem somewhere – such as a honest mistake somewhere, or someone attempting to do a malicious take-over.

    Either way, in the interim, make sure that the domain is registrar locked (not sure if Network Solutions supports it, but they suck, and you should really consider moving to another service. I find Moniker (www.moniker.com) to be great for domain management. Finally, in the DNS setup, set the name server to a shorter refresh time – perhaps 30 minutes or so – for a while. It means that it gets refreshed faster, and with some luck the problems go away faster. Not a solution, but it may kill off some of the symptoms faster whilst you find a decent solution.

    Godspeed, fella, and happy newyear 🙂

    Haje

    • Thanks. That seems to clinch it to Time Warner.

      Bright House is Time Warner. That seems to be the common thread–Time Warner and all their affiliates (RoadRunner, AOL, and so on) could not resolve the site (and were showing the wrong IP address), and everyone else could.

      Not a name server or router issue with a particular Time Warner name server, because Bright House, RoadRunner, and AOL all use different name servers, but all could not reach the site. I think they somehow grabbed the same corrupt DNS record that Network Solutions had.

  11. Valid here

    Valid here too. Apple Corp via att. No issues in our NAT based DMZ either which can be “brittle” on occasion.

    Partial traceroute included below. Looks like your host blocks at the inbound in their DMZ

    traceroute to obsidianfields.com (64.202.163.7), 64 hops max, 40 byte packets
    1 17.—.—.— (17.—.—.—) 1.080 ms 0.315 ms 0.273 ms
    2 17.—.—.— (17.—.—.—) 0.558 ms 0.309 ms 0.354 ms
    3 carter-10 (17.200.24.7) 0.449 ms 0.367 ms 0.331 ms
    4 10.15.6.193 (10.15.6.193) 0.388 ms 0.380 ms 0.336 ms
    5 10.15.6.17 (10.15.6.17) 0.362 ms 0.525 ms 0.357 ms
    6 12.118.116.9 (12.118.116.9) 1.302 ms 1.105 ms 1.202 ms
    7 tbr1-p010801.sffca.ip.att.net (12.122.80.218) 23.254 ms 23.097 ms 23.249 ms
    8 tbr1-cl3.la2ca.ip.att.net (12.122.10.26) 22.789 ms 22.718 ms 22.936 ms
    9 tbr2-p012501.la2ca.ip.att.net (12.122.9.146) 24.301 ms 23.638 ms 23.470 ms
    10 gbr2-p20.sd2ca.ip.att.net (12.122.11.254) 21.966 ms 21.644 ms 21.332 ms
    11 gbr1-p60.sd2ca.ip.att.net (12.122.1.109) 21.606 ms 21.929 ms 21.670 ms
    12 gbr1-p20.phmaz.ip.att.net (12.122.2.5) 21.954 ms 22.017 ms 21.834 ms
    13 gar2-p360.phmaz.ip.att.net (12.123.142.45) 21.753 ms 21.765 ms 21.848 ms
    14 mdf1-gsr12-1-pos-7-0.phx1.attens.net (12.122.255.230) 22.017 ms 22.095 ms 22.042 ms
    15 mdf1-bi8k-1-eth-1-6.phx1.attens.net (63.241.129.130) 22.138 ms 22.044 ms 22.095 ms
    16 63.241.142.122 (63.241.142.122) 40.028 ms 39.797 ms 39.764 ms
    17 63.241.142.122 (63.241.142.122) 39.781 ms !X * *

  12. Valid here

    Valid here too. Apple Corp via att. No issues in our NAT based DMZ either which can be “brittle” on occasion.

    Partial traceroute included below. Looks like your host blocks at the inbound in their DMZ

    traceroute to obsidianfields.com (64.202.163.7), 64 hops max, 40 byte packets
    1 17.—.—.— (17.—.—.—) 1.080 ms 0.315 ms 0.273 ms
    2 17.—.—.— (17.—.—.—) 0.558 ms 0.309 ms 0.354 ms
    3 carter-10 (17.200.24.7) 0.449 ms 0.367 ms 0.331 ms
    4 10.15.6.193 (10.15.6.193) 0.388 ms 0.380 ms 0.336 ms
    5 10.15.6.17 (10.15.6.17) 0.362 ms 0.525 ms 0.357 ms
    6 12.118.116.9 (12.118.116.9) 1.302 ms 1.105 ms 1.202 ms
    7 tbr1-p010801.sffca.ip.att.net (12.122.80.218) 23.254 ms 23.097 ms 23.249 ms
    8 tbr1-cl3.la2ca.ip.att.net (12.122.10.26) 22.789 ms 22.718 ms 22.936 ms
    9 tbr2-p012501.la2ca.ip.att.net (12.122.9.146) 24.301 ms 23.638 ms 23.470 ms
    10 gbr2-p20.sd2ca.ip.att.net (12.122.11.254) 21.966 ms 21.644 ms 21.332 ms
    11 gbr1-p60.sd2ca.ip.att.net (12.122.1.109) 21.606 ms 21.929 ms 21.670 ms
    12 gbr1-p20.phmaz.ip.att.net (12.122.2.5) 21.954 ms 22.017 ms 21.834 ms
    13 gar2-p360.phmaz.ip.att.net (12.123.142.45) 21.753 ms 21.765 ms 21.848 ms
    14 mdf1-gsr12-1-pos-7-0.phx1.attens.net (12.122.255.230) 22.017 ms 22.095 ms 22.042 ms
    15 mdf1-bi8k-1-eth-1-6.phx1.attens.net (63.241.129.130) 22.138 ms 22.044 ms 22.095 ms
    16 63.241.142.122 (63.241.142.122) 40.028 ms 39.797 ms 39.764 ms
    17 63.241.142.122 (63.241.142.122) 39.781 ms !X * *

  13. Good question. Who’s your work service provider? (Anyone in the Time Warner network, by any chance?)

    It appears the problem with my Web site was a corruption in the DNS records at Network Solutions. I pointed the name servers at a bogus address, then back at the GoDaddy name servers, which forced a refresh of the record, and lo and behold, this afternoon the site started resolving for me again. It seems that it affected only people using RoadRunner/Bright House/AO/et al, so I’m wondering if they also grabbed a corrupt name server record.

    Now what’s weird is that nobody else showed the incorrect IP address, and it seems nobody else had problems. *shrug* Weird.

  14. Re: Works fine / Zen UK

    I’m in the process of transferring the registration from Network Solutions (may they rot in hell, or a place like hell), as this kind of issue has happened before. It definitely appears to have been a Network Solutions issue, though it’s working correctly now.

  15. Thanks. That seems to clinch it to Time Warner.

    Bright House is Time Warner. That seems to be the common thread–Time Warner and all their affiliates (RoadRunner, AOL, and so on) could not resolve the site (and were showing the wrong IP address), and everyone else could.

    Not a name server or router issue with a particular Time Warner name server, because Bright House, RoadRunner, and AOL all use different name servers, but all could not reach the site. I think they somehow grabbed the same corrupt DNS record that Network Solutions had.

  16. obsidianfields.com has address 64.202.163.7

    Yep, that’s correct. For some reason, Network Solutions and some ISPs (apparently, ISPs affiliated with Time Warner) up and decided a few days back that the site’s IP address was a 219.something address, which is not even close to being right.

    Right now, Time Warner is showing the correct IP address, but Network Solutions’ WHOIS information now shows the site’s IP as 1.1.1.1…weird, huh?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.