----- Pete Klein <petek1827 at yahoo dot com> wrote:
> What interface is 192.168.2.1 on?
192.168.2.1 is my monowall lan facing ip.
>Do you have more than a LAN and WAN interface on your monowall?
No this box is only capable of 2 nics.
> How is 126.96.36.199 getting assigned? Is it hard set in
> Windows or coming from monowall?
This is a good question....
In my monowall "General Setup" screen, I have 188.8.131.52 and 184.108.40.206.
I don't have any hard coded dns entries in windows, when not connected via pptp, I only have
192.168.0.1 for my dns.
I am using the dns forwarder on the monowall. But using an external dhcp server, that only delivers
192.168.2.1 for dns.
So it looks like monowall pptp is handing out the 192.168.2.1 and then one of the dns entries from
the general setup screen?
> I'm guessing but I would suspect Windows is for some
> reason unable to use dnsmasq on 192.168.2.1 (and thus
> unable to use internal names)and is falling back to
> 220.127.116.11 (and grabbing external names instead).
> If you temporarily disable assigning 18.104.22.168 does
> DNS still work?
I'm not sure how to go about disabling 22.214.171.124 from being assigned.
Here is where it gets weird, running nslookup, I get the correct internal ip address. But when
using anything else, it's resolving to the external address.
I have for a test, hard coded 192.168.2.1 as the dns server for this pptp connection, now I only see
192.168.2.1 in ipconfig for the pptp connection. But it would appear that windows is checking my
local network dns first, before checking the pptp dns.
I wrote a program that uses the windows networking api, and do some ip lookups. I see it time after
time, hitting the local dns, then the pptp dns.
I'll have to figure that mess out then. Looks like this is all windows problem.
Thanks for the help.