<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000'><font face="arial, helvetica, sans-serif"><span style="font-size: 12pt;">That's a good idea. If you aren't comfortable with Wireshark, you could try this first. From a Windows cmd box:</span></font><div><font face="arial, helvetica, sans-serif"><span class="Apple-tab-span" style="white-space:pre"> </span>ipconfig /all | findstr /C:"DNS Server"</font></div><div><font face="arial, helvetica, sans-serif"><br></font></div><div><font face="arial, helvetica, sans-serif">That should return one or more IP addresses of the regular DNS servers you have. Suppose it returns 10.1.1.5 and 10.2.1.5, from your Linux shell:</font></div><div><font face="arial, helvetica, sans-serif"><span class="Apple-tab-span" style="white-space:pre"> </span>host somefileserver.local 10.1.1.5 </font></div><div><font face="arial, helvetica, sans-serif"><span class="Apple-tab-span" style="white-space:pre"> </span>host somefileserver.local 10.2.1.5</font></div><div><font face="arial, helvetica, sans-serif">See if either of them return the IP of somefileserver.local (or whatever the hostname is you're looking for).</font></div><div><font face="arial, helvetica, sans-serif"><br></font></div><div><font face="arial, helvetica, sans-serif">If it does, then you have a regular DNS server that will respond and the issue will be your bind configuration. If it doesn't then you'll have to go another route.</font></div><div><font face="arial, helvetica, sans-serif"><br></font></div><div><font face="arial, helvetica, sans-serif">Scott<br></font><br><hr id="zwchr" style="color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: 12pt;"><div style="color: rgb(0, 0, 0); font-family: Helvetica, Arial, sans-serif; font-size: 12pt; font-weight: normal; font-style: normal; text-decoration: none;"><b>From: </b>"Derek Atkins" <warlord@MIT.EDU><br><b>To: </b>"Atlanta Linux Enthusiasts" <ale@ale.org><br><b>Sent: </b>Tuesday, March 3, 2015 9:52:59 AM<br><b>Subject: </b>Re: [ale] Linux Bind9 and Windows .local dns?<br><br>Try to set up a wireshark session to see who the windows box is actually<br>asking. Is it using mDNS or is it asking the configured DNS Server?<br>Once you see what's going over the network you might better see where<br>the issue is and try to fix it.<br><br>-derek<br><br>"Robert L. Harris" <robert.l.harris@gmail.com> writes:<br><br>> Corp is using .local for some internal services such as a key file server. I<br>> have no control over it.<br>><br>> The first key issue I'm seeing is a windows box on my 172.27 subnet can ping<br>> the file server but trying to do a dns lookup on the hostname is failing to<br>> resolve. As a result all the procedures that tell my manufacturing users to<br>> open "\\share.local\Manufacturing" fail and updating them to do \\<br>> 10.bbb.ccc.ddd\Manufacturing" would cause a lot more pain than it's worth. <br>><br>> My Linux bind server has the windows domain servers as the upstream dns in my<br>> resolv.conf but I've never had to deal with this type of forwarding before so<br>> I'm not sure where the breakage is.<br>><br>> Unfortunately we have critical documents on the shared server and I need to<br>> get it working this way.<br>><br>> Robert<br>><br>> On Mon, Mar 2, 2015 at 11:59 AM LnxGnome <lnxgnome@hopnet.net> wrote:<br>><br>> .local is a concept of multicast DNS. If the host.local speaks mDNS, it<br>> should be responding to those replies for itself. This works find for a<br>> small shared LAN.<br>> <br>> If you have a distributed / firewalled network that isn't passing mDNS<br>> between segments, that is probably causing your problem. In this<br>> situation, don't use ".local".<br>><br>> --LnxGnome<br>><br>> On 3/2/15 12:35 PM, Robert L. Harris wrote:<br>> <br>> I've set up a bind9 server ( Ubuntu ) for a subnet ( 172.27/16 ) at<br>> work to support some lab space. I've found a problem where it seems<br>> some Windows boxes are not correctly resolving the corp.local domain<br>> even though I'm referencing the corp dns servers and internal.corp.com<br>> works just fine, just not the .local. I can access with \\<br>> aaa.bbb.ccc.dd\share correctly and ping aaa.bbb.ccc.ddd without issue.<br>> <br>> Anyone seen this or have a link? Googling "linux bind9 windows domain"<br>> provides a lot of red herrings.<br>> <br>> Robert<br>><br>> _______________________________________________<br>> Ale mailing list<br>> Ale@ale.org<br>> http://mail.ale.org/mailman/listinfo/ale<br>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>> http://mail.ale.org/mailman/listinfo<br>> <br>> _______________________________________________<br>> Ale mailing list<br>> Ale@ale.org<br>> http://mail.ale.org/mailman/listinfo/ale<br>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>> http://mail.ale.org/mailman/listinfo<br>><br>> _______________________________________________<br>> Ale mailing list<br>> Ale@ale.org<br>> http://mail.ale.org/mailman/listinfo/ale<br>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>> http://mail.ale.org/mailman/listinfo<br><br>-- <br> Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory<br> Member, MIT Student Information Processing Board (SIPB)<br> URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH<br> warlord@MIT.EDU PGP key available<br><br>_______________________________________________<br>Ale mailing list<br>Ale@ale.org<br>http://mail.ale.org/mailman/listinfo/ale<br>See JOBS, ANNOUNCE and SCHOOLS lists at<br>http://mail.ale.org/mailman/listinfo<br></div><br></div></div></body></html>