DNS Issues after setting up a WAN?

Hello

We are running a network with Red Hat Enterprise Linux ES 4.
 The
network ID is 192.168.0.x.  The server IP address is
192.168.0.1.  The
sever is also acting as a DNS server.

We have configured the DNS server and it seems to be working
fine.  On
the local side of the network (Network ID 192.168.0.x) we
can ping the
server by using the server name or the FQDN.   Both the
following
commands work fine.

	ping rs-svr1
(successful ping)
	ping rs-svr1.ruclaservices.local                (successful
ping)


We then configured two routers to connect a remote site with
Network ID
192.168.1.x.  The routing table has also been set up
properly on the
server.

However, from the remote side we seem to be getting DNS
issues which is
affecting several things including proper SAMBA client
operation.  We
are not posting this in a SAMBA group because this seems to
be a
networking issue that is affecting other issues.

On the remote side, we can NOT ping using the server name
but we CAN
ping using the FQDN.

	ping rs-svr1
(unsuccessful ping)
         	ping rs-svr1.ruclaservices.local
(successful ping)


Our resolv.conf on the server seems ok.  It has the
following lines:

	domain ruclaservices.local
	search ruclaservices.local
	nameserver 192.168.0.1


When we run nslookup on a Windows PC on the remote side, we
get the
following results:

	> nslookup rs-svr1.ruclaservices.local

		Server:  rs-svr1.ruclaservices.local
		Address:  192.168.0.1

		Name:    rs-svr1.ruclaservices.local
		Address:  192.168.0.1


	> nslookup rs-svr1

		Server:  rs-svr1.ruclaservices.local
		Address:  192.168.0.1

		*** rs-svr1.ruclaservices.local can't find rs-svr1:
Non-existent domain



Can anyone tell us why this is the case and how we can not
correct it?


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

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-requestredhat.com?subject=unsubscribe
h
ttps://www.redhat.com/mailman/listinfo/redhat-list

On 12/20/06, Georges I. Carraha <CarrahaGarubadigital.com> wrote:
> Our resolv.conf on the server seems ok.  It has the
following lines:
>
>         domain ruclaservices.local
>         search ruclaservices.local
>         nameserver 192.168.0.1
>
>
> When we run nslookup on a Windows PC on the remote
side, we get the
> following results:
>
>         > nslookup rs-svr1.ruclaservices.local
>
>                 Server:  rs-svr1.ruclaservices.local
>                 Address:  192.168.0.1
>
>                 Name:    rs-svr1.ruclaservices.local
>                 Address:  192.168.0.1
>
>
>         > nslookup rs-svr1
>
>                 Server:  rs-svr1.ruclaservices.local
>                 Address:  192.168.0.1
>
>                 *** rs-svr1.ruclaservices.local can't
find rs-svr1:
> Non-existent domain
>
>
>
> Can anyone tell us why this is the case and how we can
not correct it?

It appears that the windows PC has a resolver problem. I'm
not a
windows user or admin so perhaps someone who is can be of
more help.
Is there a resolv.conf on a windows PC? What does it have in
it?
Search domains set there or somewhere else? What is the
domain of the
windows PC?

John

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-requestredhat.com?subject=unsubscribe
h
ttps://www.redhat.com/mailman/listinfo/redhat-list

On 12/20/06, Georges I. Carraha <CarrahaGarubadigital.com> wrote:
> However, from the remote side we seem to be getting DNS
issues which is
> affecting several things including proper SAMBA client
operation.  We
> are not posting this in a SAMBA group because this
seems to be a
> networking issue that is affecting other issues.
>
> On the remote side, we can NOT ping using the server
name but we CAN
> ping using the FQDN.

On your Windows PC on the "remote side", run
"ipconfig /all".

Check to see if ruclaservices.local is listed under
"DNS suffix search
list".  If not, do the following:
- Start
- Settings
- Network Connections
- (select the applicable network connection), right-click,
Properties
- On General tab, select Internet Protocol (TCP/IP),
Properties, Advanced
- Add "ruclaservices.local" under "Append
these DNS suffixes".

Alternatively, configure your DHCP server on the
"remote side" to
include that domain in the list that's passed to DHCP
clients.

HTH,
-j

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

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-requestredhat.com?subject=unsubscribe
h
ttps://www.redhat.com/mailman/listinfo/redhat-list

inode0 wrote:
> On 12/20/06, Georges I. Carraha <CarrahaGarubadigital.com> wrote:
>> Our resolv.conf on the server seems ok.  It has the
following lines:
>>
>>         domain ruclaservices.local
>>         search ruclaservices.local
>>         nameserver 192.168.0.1
>>
>>
>> When we run nslookup on a Windows PC on the remote
side, we get the
>> following results:
>>
>>         > nslookup rs-svr1.ruclaservices.local
>>
>>                 Server: 
rs-svr1.ruclaservices.local
>>                 Address:  192.168.0.1
>>
>>                 Name:   
rs-svr1.ruclaservices.local
>>                 Address:  192.168.0.1
>>
>>
>>         > nslookup rs-svr1
>>
>>                 Server: 
rs-svr1.ruclaservices.local
>>                 Address:  192.168.0.1
>>
>>                 *** rs-svr1.ruclaservices.local
can't find rs-svr1:
>> Non-existent domain
>>
>>
>>
>> Can anyone tell us why this is the case and how we
can not correct it?
> 
> It appears that the windows PC has a resolver problem.
I'm not a
> windows user or admin so perhaps someone who is can be
of more help.
> Is there a resolv.conf on a windows PC? What does it
have in it?
> Search domains set there or somewhere else? What is the
domain of the
> windows PC?
> 
> John
> 
yes, i believe this is windows problem.
if you run ipconfig from command prompt, you should have the
line like this
Connection-specific DNS Suffix: ruclaservices.local

you can add it manually in dns suffix in ip configuration in
windows 
client, or you can change it in your dhcp server.


-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-requestredhat.com?subject=unsubscribe
h
ttps://www.redhat.com/mailman/listinfo/redhat-list