02-07-2015 01:13 PM - edited 02-07-2015 01:28 PM
Well, misery loves company. I just sent a message to greenwave via their "contact us" page at: http://www.greenwavesystems.com/#contact
It more than likely has to be a firmware-related issue, which gives me some hope that it will be corrected in the not-so-distant future....(assuming someone from FIOS is actually reading these posts)!
02-08-2015 06:25 AM
Possibly, however I tried to do the same thing on my Actiontec and it does not seem to wrk there either. I never actually noticed before because I always added the statics into the drivers\etc\hosts file.
02-08-2015 07:22 AM
I had been using an Actiontec MI424WR router for 2 years prior to upgrading to the G1100 "Quantum Gateway," and I never had any issues with user-defined DNS entries. In fact, I relied on their use quite heavily (naming several key components on my LAN by name, instead of IP), which is why I am so eager to see this feature work with the G1100.
02-21-2015 08:23 PM
It's been a while for me since I setup a DNS server.
I would have server search local domain first then forward to external caching server.
The Quantum router seems to be forwarding everything by default.
I will dig further.
03-05-2015 06:41 AM
Think I figured this out (Or at least what's causing the router to mess up)
Does anyone (else, besides me) having this problem have host names with spaces in them? My two Nintendo products (a WiiU and a 3DS) both put spaces in their DHCP replies for their names (or at least spaces show up in the router's DNS Server page). I was looking at the system error log and I noticed that named was erroring out and the field it didn't like was the 2nd 'word' in the Nintendo systems' hostname. I Shut down the Nintendo devices (and putting up with the complaints from my 11 year old), rebooting the router and chaning the DHCP lease to 1 (to flush things out). Now local DNS works as expected (at least nslookup from WIndows gives the expect IP for local machines.
Not exactly problem solved, since the previous Verizon supplied router had no issue with the spaces, but at least a path to a solution (will probably try static IP and hostnames for the affected devices).
PS I haven't re-enabled the devices yet to confirm the problem resurfaces
PPS - Greenwave was less than helpful, they refered me to Verizon and told me to ask for tier 2 support. Tier 2 support told me to pound sand since I'm not a premium customer.
03-05-2015 08:39 AM
Spaces are not legal in a domain name when it comes to DNS.
Ping commands don't know how to process with a space (example: ping Robert's Wii).
Not sure why it worked on the previous version.
03-05-2015 10:50 AM
I'm going to spend part of my snowy day a little later on the phone with Nintendo, trying to see if there's a way to fix it from the that end. (At least something to do between pushing snow around the driveway!)
Perhaps off topic a little, the distinction here may be permittable spaces (or other octets) in the host vs domain/subdomain name . . .
BTW: While Windows (at least Win7 home) appears to have an issue with spaces, Linux (Fedora 21) ping and nslookup do support spaces in both host and TLD, though of course they don't resolve to anything:
[bob@xxxxxx ~]$ ping "hello world.my home"
ping: unknown host hello world.my home
[bob@xxxxx ~]$ nslookup "Hello World.My Domain"
** server can't find Hello\032World.My\032Domain: NXDOMAIN
(Interesting that nslookup errors with the octal representaion, but ping does not)
In looking at the DNS request, as captured by wireshark, in both cases the query name reflects the spaces (in both the host and TLD portion. ie the 'query' portion of the DNS request:
0000 0b 48 65 6c 6c 6f 20 57 6f 72 6c 64 09 4d 79 20 .Hello World.My
0010 44 6f 6d 61 69 6e 00 00 01 00 01 Domain..... .
Note the length fields (0b / 09) include the spaces (20)
In reading the various RFC's its a little muddy to me if spaces are legal, as there are references to octet strings as well as restiction to LetterDigitHyphen. Wikipedia (OK, not the best of references) Domain_name_system page states "DNS names may technically consist of any character representable in an octet. However, the allowed formulation of domain names in the DNS root zone, and most other sub domains, uses a preferred format and character set."
Perhaps there may be a distinction with a difference regarding host vs domain/subdomain names. In the case of the Quantum Router, its clearly a hostname containing spaces problem I believe I am seeing
In addition, RFC 2181 states:
The DNS defines domain name syntax very generally -- a string of labels each containing up to 63 8-bit octets, separated by dots, and with a maximum total of 255 octets. Particular applications of the DNS are permitted to further constrain the syntax of the domain names they use, although the DNS deployment has led to some applications allowing more general names. In particular, Section 2.1 of this document liberalizes slightly the syntax of a legal Internet host name that was defined in RFC-952 [DNS:4].
03-06-2015 09:01 AM
I have what I think is a work-around (the engineer in me) or a solution (the user support in me) to the issue of spaces in DHCP supplied host names. I’ve tested this with my Wii U and 3DS