DNS Issues after setting up a WAN?

[Georges I. Carraha]

Hello 

The result of "ipconfig /all"  from a Windows PC at the main site is as
follows:

Windows IP Configuration

        Host Name . . . . . . . . . . . . : rs-adm-02
        Primary Dns Suffix  . . . . . . . : 
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : 
        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
        Physical Address. . . . . . . . . : 00-03-47-F8-BF-F4
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.0.11
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.254
        DNS Servers . . . . . . . . . . . : 192.168.0.1



The result of "ipconfig /all"  from a PC at the remote site is as
follows:


Windows IP Configuration

        Host Name . . . . . . . . . . . . : rs-adm-01
        Primary Dns Suffix  . . . . . . . : 
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : 
        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
        Physical Address. . . . . . . . . : 00-07-E9-82-46-F3
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.1.11
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.226
        DNS Servers . . . . . . . . . . . : 192.168.0.1


If we take the PC from the remote side and simply change the IP address
and gateway, the PC then works fine at the main site.

We have done this arrangement many times before without any problems but
the only difference is that the server was a Windows server.    We had
no problems with DNS then.

I have a strong suspicion that the problem has nothing to do with the IP
configuration of the client PCs but has more to do with the way I have
set up the DNS server on the Linux server.   I believe that my
"named.conf" file and/or my DNS tables may have problems with its
configuration in the way it handles DNS requests over different subnets.




Regards,
Georges Carraha
mailto:CarrahaG at arubadigital.com
Aruba Digital Systems N.V.
Avenida Milio J. Croes 31
Oranjestad, Aruba
Dutch Caribbean
Tel:  (297) 583-9501     Fax: (297) 583-9504 


-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com] On Behalf Of Gaddis, Jeremy L.
Sent: Thursday, December 21, 2006 12:30 AM
To: General Red Hat Linux discussion list
Subject: Re: DNS Issues after setting up a WAN?

On 12/20/06, Georges I. Carraha <CarrahaG at arubadigital.com> wrote:
> The  remote side has no DHCP server.   It only consists of some
Windows
> XP PCs connected to the router and they are accessing the Linux Server

> at the main location.

Where are they getting IP addresses from?  Manually configured on the
individual workstations?  Using dhcp-relay on the router to use the same
DHCP server at $main_site?

> Also putting the ruclaservices.local as the DNS suffix does not make a

> difference.
>
> What I would like to point out is the fact that the Windows XP 
> machines at the main location are not having the same problems as the 
> ones at the remote location.

How about you paste the output from "ipconfig /all" from a) a machine at
$main_site that's working properly, and b) a machine at $remote_site
that's not?

-j

--
Jeremy L. Gaddis, MCP, GCWN
http://www.linuxwiz.net/

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list