Coast Plaza hotel has a broken(ish) DNS — most web sites won’t resolve unless you hit reload about 8 million times (or use a shell loop to ping many many times). Aargh!
But it does completely block my office’s Citrix connections, so no work e-mail for me!
Finally got something useful done with the Thinkpad with the broken backlight. Thanks to lots of help from Paul, and a critical bit of advice from Stephen, it’s now living on my network and visible to the outside world.
What had me initially confused was that both my modem (a SpeedTouch 546) and my Netgear router have NAT firewalls. I had to declare the router as a DMZ on my modem, and the Thinkpad a DMZ on my router. Also, the router’s DynDNS support was only reporting its IP address as seen behind the modem, so I had to turn that off and use dynDNS from the modem.
Security hole? Perhaps; but it’s not as if OpenBSD is the least secure or most widely-used OS. I’ve really only got sshd and thttpd running, so there’s not much to chew on …
I recently registered a domain, but couldn’t get the hosting company’s DNS to stick in the admin console page. This workaround was given to me five days ago by an NS staffer, and it works:
- set domain to point to NS’s “Under Construction” page
- log out
- log back in, and change the domain servers
- log out (again)
- log back in, and the changes will stick.