Re: [2.0] dnsmasq

On Sun, Oct 16, 2011 at 13:10:27, Michael Rasmussen wrote:

> On Sun, 16 Oct 2011 12:55:43 +0100
> Bob Brewer <[email protected]> wrote:
> 
> >
> > As suggested in this thread I have edited my /etc/rc.d/rc.dnsmasq
> file
> > to omit the "--local=/$DOMAINNAME/" suffix which has cured the
> problem
> > I was having with localdomain DNS lookups.
> >
> I still see issues related to using an internal DNS where response 
> involves CNAME. Apparently the original host header is striped-off in 
> the response resulting in broken vhost reply from Apache. Anybody 
> seeing this behavior?
> 
My IPCop uses my ISP's DNS servers, likewise PC's in GREEN/BLUE, and also
set as DNS for servers in ORANGE.
DNS servers in ORANGE are non-recursive, basically used to host zone records
for public services (web, mail, DNS).
Everything is Microsoft-based.
I have multiple static RED IP's

Here's how it works for me:
DNS servers host zone record for mydomain.com &  "A" records for
www.domain.com (live web site) and www-test.domain.com (test web site), et
al.

Live web site is hosted on server in DMZ, and once correct port forwarding
record is added via IPCop's Web GUI, is accessible to outside world.

Test web site is hosted on PC in GREEN, so I add a host record for
www-test.domain.com via IPCop's Web GUI using GREEN IP, and PC's in GREEN
(and BLUE) can access test site internally.
But, if I need to open up the test web site to an outside world viewer, I
can simply add a port forwarding rule via IPCop to make test site visible to
that viewer.
PC's in GREEN/BLUE have a variety of fixed ip addresses, and dhcp-assigned
ones with both fixed and dynamic leases.

With this setup eveything worked fine with v1.4.xx versions, but it didn't
with v2.0.0 until I made the edit to rc.dnsmasq.

Here is output from NSLOOKUP run on a GREEN pc (after rc.dnsmasq edit &
reboot):

   C:\Users\XXXX>nslookup
   Default Server:  ipcop.domain.com
   Address:  192.168.0.254
   > www-test.domain.com
   Server:  ipcop.domain.com
   Address:  192.168.0.254
   Name:    www-test.domain.com
   Address:  192.168.0.10
   > server 87.194.0.66
   Default Server:  ns1.betherenow.co.uk
   Address:  87.194.0.66
   > www-test.domain.com
   Server:  ns1.betherenow.co.uk
   Address:  87.194.0.66
   Non-authoritative answer:
   Name:    www-test.domain.com
   Address:  XXX.XXX.XXX.XXX

I've used "domain.com" here instead of the real domain name.
87.194.0.66 is the IP of one of my ISP's DNS servers.
XXX.XXX.XXX.XXX is one of my public IP addresses.

Haven't noticed any issues with this, but I'm no DNS expert :-(

John



------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct