[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: DNS Issues after setting up a WAN?



Hello 
 
We did the following on a PC on the remote side  with IP Address 192.168.1.11.
 
Without DNS suffix
==============
Test 1
Command:   ping rs-svr1
Result:         Ping request could not find host rs-svr1. Please check the name and try again.
 
Test 2
Command:   ping rs-svr1.ruclaservices.local
Result:         Ping request could not find host rs-svr1. Please check the name and try again.

Test 3
Command:   ping 192.168.0.1
Result:         
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=3ms TTL=62
Reply from 192.168.0.1: bytes=32 time=2ms TTL=62
Reply from 192.168.0.1: bytes=32 time=3ms TTL=62
Reply from 192.168.0.1: bytes=32 time=3ms TTL=62
Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 3ms, Average = 2ms


Test 4
Command:   nslookup 192.168.0.1
Result:         
Server:  UnKnown
Address:  192.168.0.1
 
 
With DNS suffix
==============
Test 5
Command:   ping rs-svr1
Result:         Ping request could not find host rs-svr1. Please check the name and try again.
 
Test 6
Command:   ping rs-svr1.ruclaservices.local
Result:         Ping request could not find host rs-svr1. Please check the name and try again.

Test 7
Command:   ping 192.168.0.1
Result:         
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=3ms TTL=62
Reply from 192.168.0.1: bytes=32 time=2ms TTL=62
Reply from 192.168.0.1: bytes=32 time=3ms TTL=62
Reply from 192.168.0.1: bytes=32 time=3ms TTL=62
Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 3ms, Average = 2ms


Test 8
Command:   nslookup 192.168.0.1
Result:         
Server:  UnKnown
Address:  192.168.0.1
 
 
 
 
Regards,
Georges Carraha
mailto:CarrahaG arubadigital com <mailto:CarrahaG arubadigital com> 
Aruba Digital Systems N.V.
Avenida Milio J. Croes 31
Oranjestad, Aruba
Dutch Caribbean
Tel:  (297) 583-9501     Fax: (297) 583-9504

________________________________

From: redhat-list-bounces redhat com on behalf of Budi Febrianto
Sent: Thu 12/21/2006 10:45 PM
To: General Red Hat Linux discussion list
Subject: Re: DNS Issues after setting up a WAN?



Georges I. Carraha wrote:
> 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  . :

>
> 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

In remote site you need to configure dns-suffix, while in main site you
don't need it. this because i believe that the server use samba to
broadcast the name.
in remote site with dns suffix enable, it automatically add the 'domain'
into the host, thus change the host of the into fqdn.
so if you ping abc, it will automatically try to use abc.domain.com

while in main site, it do not need the dns-suffix, because it will use
the name that broadcast from the computer. for small lan it can works,
but for big lan, it usually failed.

usually we add the dns suffix in dhcp server, but for small lan, we can
add it manually.

dns suffix similar with search entry in resolve.conf.

try to add dns suffix in your remote client, and see if that works.

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





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]