Windows 2003 Server / DNS issues

Khad · 03-04-2008, 02:05 AM

Hi everybody,

I've come across something I can't figure out, maybe someone already experienced this and hopefully will be able to help.

Here's the setup :
- a network segment where many servers (Windows/Linux) are connected (say 192.168.1.0)
- each server has a second NIC connected to a second network segment : 192.168.2.0 (this is for inter-server communications so that bandwith is saved on the other segment)
- two domain controllers

A server named test1.domain.local has 2 ip addresses (192.168.1.45 and 192.168.2.45). If the resolution is done from the 192.168.1.0 network, I get the 192.168.1.45 IP. If the resolution is done from the 192.168.2.0 network, I get the 192.168.2.45 IP. Everything is fine, the dns server knows where I'm coming from so it gives me the right IP address.

The problem comes when I'm coming from another network. When I'm connected through a VPN, my ip address is in the 192.168.3.0 network. When I try to resove test1.domain.local it seems that the dns server sometimes gives me the 192.168.1.45 address, sometimes it gives me the 192.168.2.45 address. The problem is that from the 192.168.3.0 I can't (and shouldn't) access the 192.168.2.0 network.

So, my question is : is it possible to configure the Microsoft DNS server to always resolve to the 192.168.1.0 network, except when coming from the 192.168.2.0 network ?

I hope this is clear enough, don't hesitate to ask for more details if what I write is not understandable...

Thanks,

Khad

animesh_joshi · 03-04-2008, 09:51 PM

When you log into a network via VPN then your IP address is encapsulated with the logged in network's IP address. Sometimes you are encapsulated with 1.0/24 and sometimes 2.0/24. You can define your specifications in the RRAS wizard to allow users to only connect to the 1.0/24 network.

Khad · 03-05-2008, 12:13 AM

Hello animesh_joshi,

I connect by OpenVPN so for the DNS servers it looks like someone from anoher network asks for a name resolution. I think there's some kind of round robin, that's why I get one IP and the other afterwards.

RRAS has nothing to do with it...

Thanks anyway.

animesh_joshi · 03-05-2008, 09:15 PM

Doesn't matter if its OpenVPN or something else. If you have configured VPN access via RRAS then you will have full control over you remote connection. The DNS doesn't resolve name depending of the source's IP address. It resolves name on the basis of the zone file entry.

Have a nice day.

03-04-2008, 02:05 AM	#1 (permalink)
Khad Registered User Join Date: Mar 2008 Posts: 4 OS: Windows XP Pro	Windows 2003 Server / DNS issues Hi everybody, I've come across something I can't figure out, maybe someone already experienced this and hopefully will be able to help. Here's the setup : - a network segment where many servers (Windows/Linux) are connected (say 192.168.1.0) - each server has a second NIC connected to a second network segment : 192.168.2.0 (this is for inter-server communications so that bandwith is saved on the other segment) - two domain controllers A server named test1.domain.local has 2 ip addresses (192.168.1.45 and 192.168.2.45). If the resolution is done from the 192.168.1.0 network, I get the 192.168.1.45 IP. If the resolution is done from the 192.168.2.0 network, I get the 192.168.2.45 IP. Everything is fine, the dns server knows where I'm coming from so it gives me the right IP address. The problem comes when I'm coming from another network. When I'm connected through a VPN, my ip address is in the 192.168.3.0 network. When I try to resove test1.domain.local it seems that the dns server sometimes gives me the 192.168.1.45 address, sometimes it gives me the 192.168.2.45 address. The problem is that from the 192.168.3.0 I can't (and shouldn't) access the 192.168.2.0 network. So, my question is : is it possible to configure the Microsoft DNS server to always resolve to the 192.168.1.0 network, except when coming from the 192.168.2.0 network ? I hope this is clear enough, don't hesitate to ask for more details if what I write is not understandable... Thanks, Khad Last edited by Khad; 03-04-2008 at 02:06 AM.

03-04-2008, 09:51 PM	#2 (permalink)
animesh_joshi Registered User Join Date: Sep 2007 Location: Melbuorne Posts: 45 OS: Win XP	Re: Windows 2003 Server / DNS issues When you log into a network via VPN then your IP address is encapsulated with the logged in network's IP address. Sometimes you are encapsulated with 1.0/24 and sometimes 2.0/24. You can define your specifications in the RRAS wizard to allow users to only connect to the 1.0/24 network.

03-05-2008, 12:13 AM	#3 (permalink)
Khad Registered User Join Date: Mar 2008 Posts: 4 OS: Windows XP Pro	Re: Windows 2003 Server / DNS issues Hello animesh_joshi, I connect by OpenVPN so for the DNS servers it looks like someone from anoher network asks for a name resolution. I think there's some kind of round robin, that's why I get one IP and the other afterwards. RRAS has nothing to do with it... Thanks anyway.

03-05-2008, 09:15 PM	#4 (permalink)
animesh_joshi Registered User Join Date: Sep 2007 Location: Melbuorne Posts: 45 OS: Win XP	Re: Windows 2003 Server / DNS issues Doesn't matter if its OpenVPN or something else. If you have configured VPN access via RRAS then you will have full control over you remote connection. The DNS doesn't resolve name depending of the source's IP address. It resolves name on the basis of the zone file entry. Have a nice day.