LAN hosts not resolving for xxx.local DNS lookups
LAN hosts not resolving for xxx.local DNS lookups
I have a LAN using the extension of ".local" with NAS, printers, systems, etc. After a power outage due to storms I find that hosts on the LAN have issues resolving for printers and my NAS. When I ping them from the client they cannot be resolve. If I ping the IP all is fine. I do a nslookup for the name nothing, nslookup of the IP nothing. If I go to the FW which is my DNS and DHCP server (all my local hosts that I know of get Static DHCP reservations) it can ping the FQN and the IP.
I have a combo of Windows, OSX, and Linux hosts all with issues.
I reading some other articles I "think" that DNS domains like ".local" are becoming reserved by apple, google, linksys, etc -- although I cannot find that printed exactly.
So *IF* .local is reserved what is a good name for a LAN home network? If home, mine, etc safe?
if .local is up for grabs then any other ideas?
Cheers!
I have a LAN using the extension of ".local" with NAS, printers, systems, etc. After a power outage due to storms I find that hosts on the LAN have issues resolving for printers and my NAS. When I ping them from the client they cannot be resolve. If I ping the IP all is fine. I do a nslookup for the name nothing, nslookup of the IP nothing. If I go to the FW which is my DNS and DHCP server (all my local hosts that I know of get Static DHCP reservations) it can ping the FQN and the IP.
I have a combo of Windows, OSX, and Linux hosts all with issues.
I reading some other articles I "think" that DNS domains like ".local" are becoming reserved by apple, google, linksys, etc -- although I cannot find that printed exactly.
So *IF* .local is reserved what is a good name for a LAN home network? If home, mine, etc safe?
if .local is up for grabs then any other ideas?
Cheers!
Shaun Vermaak
Add an xxx.local zone to your DNS and add all those devices to register against it or add static entries for those who can't
ASKER
so just a clarification when you have a host register with DHCP -- it doesn't also register with DNS? So in other words when you do want to have a local LAN setup use DHCP with the MAC addr which will map to the IP, but then you also need a DNS entry to map that IP to a FQN?
I don't know why I thought that DHCP did that automagically.
I don't know why I thought that DHCP did that automagically.
It does but the zone needs to exist and DHCP needs to point it to the correct DNS server that hosts this zone
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
looking at the DHCP server it is using isc-dhclient and the /etc/dhcp/dhclient.conf file doesn't hold much. Everything is commented out save for:
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
dhcp6.name-servers, dhcp6.domain-search,
netbios-name-servers, netbios-scope, interface-mtu,
rfc3442-classless-static-r
The DNS seems to be dnsmasq.
And since I do have OSX as my primary workstation(s) ".local" is a bad choice.
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
dhcp6.name-servers, dhcp6.domain-search,
netbios-name-servers, netbios-scope, interface-mtu,
rfc3442-classless-static-r
The DNS seems to be dnsmasq.
And since I do have OSX as my primary workstation(s) ".local" is a bad choice.
Not a bad choice per se, but you may need to install avahi on your linux system to help resolve using mdns.
(You can check with tcpdump / tshark / wireshark ) up front if mdns is on your network...
check with capture filter: 'udp port 5353'
if it shows traffic you can find the sources by looking at the UDP sources addresses
(You can check with tcpdump / tshark / wireshark ) up front if mdns is on your network...
check with capture filter: 'udp port 5353'
if it shows traffic you can find the sources by looking at the UDP sources addresses
FW which is my DNS and DHCP
Since you had a power outage that implies to me that the FW has a saved and a running configuration and the running configuration wasn't saved.. go back into the FW settings and reconfigure things to the way they were.
Since you had a power outage that implies to me that the FW has a saved and a running configuration and the running configuration wasn't saved.. go back into the FW settings and reconfigure things to the way they were.
ASKER
I am using an untangled FW appliance so yes it does have a running and a saved config. So far I can only save items that they allow via the web GUI interface.
I do have everything on an UPS, so the shutdown is controlled, but the UPS just give me time to shut all my devices down.
Believe it or not this is just a home network, but being a geek I do love to experiment hence all the hardware and virtual stuff.
I do have everything on an UPS, so the shutdown is controlled, but the UPS just give me time to shut all my devices down.
Believe it or not this is just a home network, but being a geek I do love to experiment hence all the hardware and virtual stuff.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I chose this as the best — it proved that ".local" is pseudo reserved. And the solution *for me* is to still use DHCP for registration and also manual create DNS records for my most important ones. The Untangle / ISC-client doesn't seem to allow for direct DNS registration. :(
thank you to all who helped. I wanted to share the solution but could only seem to find one means to grant "best solution"
thank you to all who helped. I wanted to share the solution but could only seem to find one means to grant "best solution"
ISC DHCP prefers DHCP server based registration. (client based registration will create administrative chaos)
Think laptop-x connects..., get address 192.168.0.1 registers as laptop-x.example.org cable get pulled...
after release time laptop-y connects... gets address 192.168.0.1 and registers as laptop-y.example.org ....
Now there are two A records: laptop-x.example.org and laptop-y.example.org both pointing to 192.168.0.1
and two 192.168.0.1 PTR record to both....
With a DHCP server managing DNS at end of lease it will pull all DNS records from the database, so there is cleaning up included for free.
In you case you can also try to install / activate AVAHI (the mDNS) client/server that is what this whole .local is meant for.
Think laptop-x connects..., get address 192.168.0.1 registers as laptop-x.example.org cable get pulled...
after release time laptop-y connects... gets address 192.168.0.1 and registers as laptop-y.example.org ....
Now there are two A records: laptop-x.example.org and laptop-y.example.org both pointing to 192.168.0.1
and two 192.168.0.1 PTR record to both....
With a DHCP server managing DNS at end of lease it will pull all DNS records from the database, so there is cleaning up included for free.
In you case you can also try to install / activate AVAHI (the mDNS) client/server that is what this whole .local is meant for.