Nov 23, 2009
I recently upgraded my FiOS service and had a problem resolving some DNS names. The solution was simple but frustrating.
I've been using Verizon FiOS for Internet service for years. In general I've been pleased with the service: it's very fast and very reliable.
I've been running FiOS without using the Verizon supplied router. Instead, I plugged the incoming CAT5 cable directly into my Linux server. This did require that I use a slightly complicated configuration supporting PPPoE, but once I finally got it set up it has been problem-free. My Linux server has also been my DNS server and my DHCP server. I'm sure Verizon doesn't like this configuration, as it gives them less control over and less visibility into my network. But that's fine with me.
However, I recently switched to using FiOS TV. Because of the way the TV set top boxes (STB's) need to communicate upstream for program information, I'm forced to use the ActionTec router that Verizon supplies. As long as I'm forced to use this router I decided to use a more normal, less techy configuration and just let the ActionTec be my DNS and DHCP server. This has generally worked without issue, at least for the first few days.
Last night I decided to change the default domain name that the router uses. It defaults to "home", but it's better for me if it uses "trueblade.com", that way I can more easily resolve domain names. In any network I've ever worked on, this would not be a problem. The only thing it should affect is that when a client asks for a name like "mail", it would first query for "mail.trueblade.com".
However this morning my home network wasn't able to connect to my mail servers. After a lot of poking around I discovered that my internal systems were not able to resolve fully qualified DNS names like mail.trueblade.com. After a lot more poking around, I discovered that the ActionTec would not resolve domain names ending in trueblade.com if its default domain were also trueblade.com.
So the solution was simply to change the default domain name on the ActionTec back to "home", or indeed any other string. That's frustrating, because it means that I can't type domain names like "mail", but I need to use the fully qualified "mail.trueblade.com". But it's only a minor frustration. The only time I don't use fully qualified names is when I'm debugging. All of my systems use fully qualified names for their configuration files.
I'll probably switch away from using the ActionTec as my DNS and DHCP servers. In addition to this problem, you're limited in the amount of configuration you have over the DHCP server in particular. I'll post more when I've made the decision to switch off of the ActionTec for DNS and DHCP.
May 14, 2009
I've been visiting Taiwan since 1990 and the Internet here keeps getting better each year. Below are some notes on my experiences.
Internet connectivity in Taiwan for residential users is available from the Cable TV company or via DSL, similar to the USA.
The residence where I'm staying uses a DSL vendor known as KBT or KB Telecom. KBT enforces PPPoE, but the Linksys WRT-54G router I installed handles the chore of establishing and maintaining the PPPoE connection.
The monthly service cost is NT$393 for the ADSL fee from www.hinet.com + NT$279 for the ISP, www.kbtelecom.com. So the total monthly service cost is NT$672 with a one year commitment. At today's exchange rate of US$1 = NT$32.864 the monthly cost is $20.45, including all taxes. The service is rated at 2Mbps down and 256 Kbps up. Such a deal!
The service is reliable and the Internet speeds are excellent. I'm getting 1,362 Kbps down and 207 Kbps up to Speakeasy's Seattle, Washington servers. Here's a comparison of the measured bandwidth from various ISPs.
I'm having no problem getting work done with our company's IMAP server & Plone webservers in New York and Virginia.