router does not resolve fonera to itself

[chirag.sanghavi@…]

Before upgrade to the beta, I was able to get to router's dashboard using  http://fonera. Now it does not work. I need to connect to it using IP Address.

[alex.roc08]

Try this

 http://fonera.local.

[chirag.sanghavi@…]

fonera.local does not resolve either.

[chirag.sanghavi@…]

I am now testing 2.3.7.0 Beta 2 - the problem continues there.

Following does resolve to the router: registerlafonera.fon.com

I checked /etc/hosts on the router, it has following:

127.0.0.1 localhost localhost. 192.168.10.1 registerlafonera.fon.com www.registerlafonera.fon.com fonera lafone ra myfonera

Ideally, the router should add all of these entries into its own dns cache (as it is the DNS server for all the clients, it should resolve that to itself).

Here is the output of

nslookup

on the fonera:

root@Fonera:/etc# nslookup lafonera
Server:    205.152.37.23
Address 1: 205.152.37.23 dns.asm.bellsouth.net

Name:      lafonera
Address 1: 192.168.10.1 registerlafonera.fon.com
root@Fonera:/etc#

when the same command is executed onto a client that is connected to the router:

C:\Users\csanghavi>nslookup
Default Server:  registerlafonera.fon.com
Address:  192.168.10.1

> lafonera
Server:  registerlafonera.fon.com
Address:  192.168.10.1

*** registerlafonera.fon.com can't find lafonera: Non-existent domain
>

[matthijs]

That fonera.local does not work is expected: the .local domain is used for zeroconf/mdns/bonjour, which Windows does natively support (It's mainly used on MacOS).

I can't figure out why "fonera" or "lafonera" are not resolving for you. It looks like your Windows client is asking the DNS server running on the Fonera (dnsmasq), since it uses 192.168.10.1 as the DNS server. Also, on the Fonera, /etc/hosts is configured correctly, and it should be loaded by dnsmasq.

• Could you check that the dns domain / search domain is set to "lan" for your connection?
• Could you try pinging "lafonera.lan" instead?
• Could you try running the following commands and paste the output here? You'll have to get the process id for dnsmasq from the output of the first command (first number on the line) and use it in the second command, as I have done in this example:

  root@Fonera:~# ps aux | grep dnsmasq | grep -v grep
   2837 nobody    2096 S    /usr/sbin/dnsmasq -K -D -y -Z -b -E -s lan -S /lan/ -
  root@Fonera:~# cat /proc/2837/cmdline 
  /usr/sbin/dnsmasq-K-D-y-Z-b-E-slan-S/lan/-l/tmp/dhcp.leases-r/tmp/resolv.conf.auto
  --dhcp-range=lan,192.168.1.100,192.168.1.250,255.255.255.0,12h-2ppp0
  --dhcp-hostsfile=/tmp/dhcp_hostsroot@Fonera:~#
  

[chirag.sanghavi@…]

I am running Windows 7 on my network.

1. This is what I see for the domain suffix

Windows IP Configuration

   Host Name . . . . . . . . . . . . : ACTUALNAMEREMOVED
   Primary Dns Suffix  . . . . . . . : us.mycompany.com
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : us.mycompany.com
                                       mycompany.com
                                       europe.mycompany.com
                                       asia.mycompany.com

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : lan
   Description . . . . . . . . . . . : Dell Wireless 1490 Dual Band WLAN Mini-Ca
rd

Primary connect search does not have search suffix of .lan, instead it has all the domains of my workplace.

I am able to resolve all of following correctly: * fonera.lan * lafonera.lan * myfonera.lan * lafonera

root@Fonera:/etc# ps aux | grep dnsmasq | grep -v grep
 3112 nobody    1840 S    /usr/sbin/dnsmasq -K -D -y -Z -b -E -s lan -S /lan/ -
root@Fonera:/etc# cat /proc/3112/cmdline
/usr/sbin/dnsmasq-K-D-y-Z-b-E-slan-S/lan/-l/tmp/dhcp.leases-r/tmp/resolv.conf.auto--dhcp-range=lan,192.168.10.100,192.168.10.250,255.255.255.0,12h-2ppp0root@Fon

[chirag.sanghavi@…]

Finally, I was able to connect. The issue was definitely with lan prefix. On a new laptop (non-work) settings are as below:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : mycomputer
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Broadcast
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : lan

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : lan
   Description . . . . . . . . . . . : Dell Wireless 1395 WLAN Mini-Card
   Physical Address. . . . . . . . . : 00-1F-E1-3C-EC-0E
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5526:de7e:7469:52d8%9(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.10.224(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, January 11, 2012 7:45:52 PM
   Lease Expires . . . . . . . . . . : Thursday, January 12, 2012 7:45:51 AM
   Default Gateway . . . . . . . . . : 192.168.10.1
   DHCP Server . . . . . . . . . . . : 192.168.10.1
   DHCPv6 IAID . . . . . . . . . . . : 167780321
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0F-BF-C9-6C-00-1D-09-5D-14-12
   DNS Servers . . . . . . . . . . . : 192.168.10.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

[matthijs]

So on this new laptop you could connect to "fonera" without problems? Or did you have to change anything to make it work?

[matthijs]

Looking at this with a fresh perspective, I suddenly realize what is happening:

• On your work laptop, the search domain is not taken from the Fonera, through DHCP, but it is configured to always use your company's domain instead. This explains why "fonera" does not work, but "fonera.lan" does.
• In addition to using DNS for name resolution, windows can also use the windows file sharing protocol (SMB) for name resolution. The fonera also supports this, but only using the "lafonera" name. This explains why "lafonera" did work.
• On your other laptop, the search domain is configured as normal, which explains why everything works there.

Given the above, this is something we can't fix in the Fonera. Your work laptop's settings prevent the name resolution from working. So, I'm closing this ticket.