www.LabVIEW.com ≠ www.ni.com/labview

[TCPlomp]

Strane is that Robtex was able to capture a labview.com screenshot that looked recent.

It might be a localized issue.

I'm from the netherlands and you?

(sometimes software developers forget that you can use a computer with a decent timestamp)

And the Robtex report suggested that it might be wise to move one of the nameservers out of the natinst.com realm.

Ton

[JackDunaway]

I'm in the United States, in the same timezone as Austin. Are you saying that labview.com works for you, Ton?

[JackDunaway]

---

TCPlomp wrote:

Strane is that Robtex was able to capture a labview.com screenshot that looked recent.

---

 The screenshot does not look recent to me... it says "Introducing LabVIEW 8.6"!!!

 

[Hornless.Rhino]

Same issues in Australia.

Visit www.labview.com and get

---

Invalid URL

The requested URL "/", is invalid.

---

Visit labview.com  (note the lackof www)

---

While trying to retrieve the URL: http://labview.com/

The following error was encountered:

Unable to determine IP address from host name for labview.com

The dnsserver returned:

No DNS records

This means that:

The cache was not able to resolve the hostname presented in the URL. 
 Check if the address is correct. 

---

[JackDunaway]

Still does not redirect.

[Laura F.]

I've noticed that it's still not working outside of our firewall as well.  The web team is aware of the issue and is further investigating.

Sorry for the delay,

Laura

[JackDunaway]

For the first time in over six weeks, today I did not receive an HTTP 400 Error. Instead, it looks like we're making some progress... or the Web Team is going for more of a "parked" look and feel:

[JackDunaway]

For the first time in seven weeks, www.LabVIEW.com = www.ni.com/labview. Resolved.

[JackDunaway]

Well, it worked at work 1.5hours ago, and now it's not working at home from a different ISP. Issue not resolved, the clock starts ticking again at seven weeks and counting.

[RavensFan]

Perhaps it will just take a little bit of time for the network mappings to propagate to the different DNS servers.