Sounds like a search suffix is getting involved: After failing to find myhostess. your resolver looks for <a href="http://myhostess.X.com">myhostess.X.com</a>. which finds the alias. /etc/resolv.conf should contain the directives which control search suffix.<div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Dec 4, 2012 at 4:44 PM, Lovelady, Dennis E. <span dir="ltr"><<a href="mailto:dlovelady1@dtcc.com" target="_blank">dlovelady1@dtcc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal">I run a domain, which I’ll call Z.com. There are two offices (<a href="http://atl.Z.com" target="_blank">atl.Z.com</a>, <a href="http://tam.Z.com" target="_blank">tam.Z.com</a>). There is also a
<a href="http://www.Z.com" target="_blank">www.Z.com</a> hosted outside these networks, and the Hosting Provider provides an alias to that, known simply as “Z.com.” All pretty simple.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Since each office is independent, I have kept a simple DNSMASQ configuration, which you can see below. (There were attempts to set up <a href="http://atl.Z.com" target="_blank">atl.Z.com</a> and <a href="http://tam.Z.com" target="_blank">tam.Z.com</a> in each office’s DNSMASQ configuration, but these were met with difficulties
now forgotten. I think the difficulty was an issue with web server not coming up. If it’s important to resolution, I will pursue again and report the issues, but let’s get to the heart of the topic.)<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Everything works OK until an incorrect hostname (or the name of a host that happens to be down) is referenced in either office. For example, if I type “ssh myhostess” and there is no “myhostess” on the current network, then the name is
magically resolved to the <a href="http://www.Z.com" target="_blank">www.Z.com</a> address, and I get the password prompt from there. Not what I’d want; I’d prefer the lookup to fail - which would then fail the ssh command - but I don’t see a way to make that happen.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Is there something I can do in this configuration to cause, for example, <a href="http://lists.thekelleys.org.uk" target="_blank">lists.thekelleys.org.uk</a> to be resolved externally, but to keep the Z.com stuff between the walls? And would this in fact be squared away by pursuing the <a href="http://atl.Z.com" target="_blank">atl.Z.com</a>
(etc.) concept? (I fear that would not resolve this.) I could remove the alias to simply Z.com, and that might do it, but I’d prefer not to do that, and anyway I’m not sure why it would fix this.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I have the following DNS configuration in each office. The dhcp-boot is not used at present, so may not be quite up to snuff.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p>domain-needed<u></u><u></u></p>
<p>bogus-priv<u></u><u></u></p>
<p>expand-hosts<u></u><u></u></p>
<p>domain=Z.com<u></u><u></u></p>
<p>dhcp-range=192.168.158.10,192.168.158.109,7d<u></u><u></u></p>
<p>dhcp-host=88:87:17:12:69:4d,canon-8120<u></u><u></u></p>
<p>dhcp-host=00:23:8b:8a:ad:70,aspire<u></u><u></u></p>
<p>dhcp-host=00:26:F2:DB:95:0C,stora-0<u></u><u></u></p>
<p>dhcp-host=C0:3F:0E:BC:43:B9,stora-2<u></u><u></u></p>
<p>dhcp-host=e0:91:f5:7c:7c:56,stora-3<u></u><u></u></p>
<p>dhcp-option=option:router,192.168.158.1<u></u><u></u></p>
<p>dhcp-boot=pxelinux.0<u></u><u></u></p>
<p>dhcp-boot=aspire-lucid/pxelinux.0<u></u><u></u></p>
<p>dhcp-match=set:gpxe,175 # gPXE sends a 175 option.<u></u><u></u></p>
<p>enable-tftp<u></u><u></u></p>
<p>tftp-root=/home/tftpd<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<br>_____________________________________________________________
<font><br>
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.</font><br>
_______________________________________________<br>
Dnsmasq-discuss mailing list<br>
<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br>
<a href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss" target="_blank">http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss</a><br>
<br></blockquote></div><br></div>