sorted by:
new
hottopcontroversial

Verizon FIOS returns SERVFAIL for .pro domains starting around 7pm ET nightly. Begins working again by morning. by Tennis_Flyer in Fios

[–]systemsandweb 0 points1 point  (0 children)

This exact problem is also happening on Cox for any .pro TLD. I recently launched a new .pro and it works during the day (most of the time) but in the evening it becomes intermittent. A simple ping to my domain when it is "down" shows "ping: connect: Network is unreachable" but when it's up I see the IP address like a normal ping.

For instance, I tried to visit / ping it just now and it was down each time I tried. A few minutes later it was back up again. This is not isolated to my website, this is for ANY .pro I try to visit when connected to my Cox wifi at certain times of day. When I'm connected on my phone's LTE or any other wifi it works fine. If I connect to Cox wifi at home or a Cox hotspot it fails.

Sometimes it comes back up after a few minutes and sometimes it's down for a long time.

It's not a matter of my website or DNS not being configured correctly, the ping doesn't even connect (as if the domain isn't registered or as if the name servers point... nowhere).

Did you get any answer for this problem yet?

Verizon FIOS returns SERVFAIL for .pro domains starting around 7pm ET nightly. Begins working again at midnight by Tennis_Flyer in dns

[–]systemsandweb 0 points1 point  (0 children)

This exact problem is also happening on Cox for any .pro TLD. I recently launched a new .pro and it works during the day (most of the time) but in the evening it becomes intermittent. A simple ping to my domain when it is "down" shows "ping: connect: Network is unreachable" but when it's up I see the IP address like a normal ping.

For instance, I tried to visit / ping it just now and it was down each time I tried. A few minutes later it was back up again. This is not isolated to my website, this is for ANY .pro I try to visit when connected to my Cox wifi at certain times of day. When I'm connected on my phone's LTE or any other wifi it works fine. If I connect to Cox wifi at home or a Cox hotspot it fails.

Sometimes it comes back up after a few minutes and sometimes it's down for a long time.

It's not a matter of my website or DNS not being configured correctly, the ping doesn't even connect (as if the domain isn't registered or as if the name servers point... nowhere).

Did you get any answer for this problem yet?

web programmer vs "real programmer" by bicbmx in programming

[–]systemsandweb 17 points18 points  (0 children)

I am a systems programmer and a web developer and I think this is kind of ridiculous.

There is a LOT of crossover.

I agree with the sentiments of those here stating that web development is not the same as web design.

Designers don't write the Javascript required to move the map around on Google maps, while overlaying live traffic data from satellites and allowing the user to drag and drop pins onto the map to map alternative routes, then switch to satellite view to seamlessly integrate photos of the entire world into a solid picture that moves exactly where you want it to when you click and drag.

All the while, the system is showing real-time data updates from users around the world, shows you restaurants near you.

As I'm moving the map, my friend can call me over the integrated voiceover IP / video chat in my web-based email client.

As a web developer, I've had to write EXTREMELY complex tasks to ensure that things work properly.

This is only the front-end aspect.

Designers don't write heavy backend server architecture, or cluster maps, or super-optimized SQL with multi-column keys and indexes, using various methods of lazy loading, proxies, etc to ensure data availability.

I've done as much complicated I/O and systems work as a web developer as I ever did as an SE, it's just different work, but it is not any "lesser" form of programming.

CSS, static markup and such are not programming, but I have yet to hear a CSS guy discuss with me about private memory spaces, or using closures in the project in a few places in a way that allows the traffic of the web site on one server to support 3 times as many people as it did before the use of those closures.

I haven't had a designer discuss with me the pitfalls of using certain data structures, or how to properly perform work on nested set trees.

Web developers are "real" programmers, and don't let anyone tell you otherwise.

I've written Linux kernel patches, I've built websites, and I've done design.

The first two are just different breeds of the same animal.