Felipe,
Thank you for your response. Let me clarify further:
On Tue, Apr 1, 2008 at 1:41 PM, Filipe Brandenburger
<filbranden@xxxxxxxxx> wrote:
> What is the IP address of your DNS server? What is the IP adress of
> the DNS server for company.com? What are the contents of the
> resolv.conf file on the machine you're testing?
DNS server (myhost.lab.company.com) - 192.168.17.2
DNS server (ns.company.com) - 10.100.1.24
1. ping/nslookup from myhost.lab.company.com
- /etc/resolv.conf -->
search lab.company.com
nameserver 127.0.0.1
ping ns
ping: unknown host ns
[root@myhost named]# ping ns.company.com
PING ns.company.com (10.100.1.24) 56(84) bytes of data.
64 bytes from 10.100.1.24: icmp_seq=1 ttl=127 time=0.123 ms
64 bytes from 10.100.1.24: icmp_seq=2 ttl=127 time=0.136 ms
2. ping/nslookup from workstation in company.com
- /etc/resolv.conf -->
search company.com
nameserver 10.100.1.24
ping myhost
ping: unknown host myhost
png myhost.lab.company.com
PING myhost.lab.company.com (192.168.17.2)56(84) bytes of data.
64 bytes from 10.100.1.24: icmp_seq=1 ttl=127 time=0.123 ms
64 bytes from 10.100.1.24: icmp_seq=2 ttl=127 time=0.136 ms
>
> Basically on your server (the one for lab.company.com) you should have
> a forwarders entry pointing to the IP of the DNS server for
> company.com.
i have created a FORWARD zone for "mycompany.com" ... snippet of
/etc/named.conf:
zone "mycompany.com." IN {
type forward;
forwarders { 10.100.1.24 port 53;
};
>
> In the other DNS server, the one that handles company.com, you should
> have in the company.com zone an NS entry for the "lab" name pointing
> to the IP of your DNS server, the one for lab.company.com.
>
The Corporate system administrator has added a zone for
lab.company.com and even a reverse zone ....
.............
After I reviewed all my configuration based on your note ... I retried
the pinging/nslookup, the following is the error I have noticed in my
/var/log/messages:
NetworkManager: <WARNING> add_ip4_config_to_named (): Could not
set forwarders for zone '.'. Error: 'Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.'.
.... Could this mean that the "company.com" DNS server is not
configured properly?
thanks in advance!
> HTH,
> Filipe
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
--
best,
Vince
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
