2 DNS server has different domains.

[chirashi]

Hey guys I have 2 domain with their own DNS server. The first one is
abc.com and the second is 123.com they are both replicating to each other
but here the thing. When I am on abc.com and I try to ping a server like
this " ping server1.123.com" I get a unknow host, but if I ping "ping
server1" I get a reply just fine. Is there a way that I can ping the full
quality domain name? Please advise

 

[Kevin Goodknecht]

In

Hey guys I have 2 domain with their own DNS server. The first one is
abc.com and the second is 123.com they are both replicating to each
other but here the thing. When I am on abc.com and I try to ping a
server like this " ping server1.123.com" I get a unknow host, but if
I ping "ping server1" I get a reply just fine. Is there a way that I
can ping the full quality domain name? Please advise

Does each DNS server have a zone for both domains?
Kinda hard to figure id like to see a nslookup with the "set d2" switch for
the FQDN and the host.
I'm thinking it could be a search order problem.

 

[TIM ROBERTS]

In oder to resolve host names in the other domain you can use a suffix
search order list and secondary zone of the other dns server

 

[Jonathan de Boyne Pollard]

c> When I am on abc.com and I try to ping a server like this
c> ping server1.123.com
c> I get a unknow host, but if I ping
c> ping server1
c> I get a reply just fine.

DNS lookup of the name->address mapping for "server1.123.com."
is returning a "no such name" error; and either
(a) "ping" is performing the name->address mapping for
the name "server1" using some other lookup mechanism,
such as NetBIOS,
or
(b) the search path mechanism in your DNS Client is
configured such that the fully qualified domain name
that your DNS Client changes "server1" into is not,
in fact, "server1.123.com." at all.

Fix your DNS service so that name->address lookup for
"server1.123.com." yields an "A" resource record set.

c> Is there a way that I can ping the full quality [sic] domain name?

Yes: Add a full stop to the end. Fully qualified domain names end
with full stops.

 

[chirashi]

Thanks guys but it didn't do the trick whenever I am on 123.com and I try to
ping the server1 I would get a reply but when I get I try server1.123.com
still no dice any other suggestion. I will tell you that it looks like both
Forward Zones are there. I can see both 123.com and abc.com in the forward
zone and under that I see the other server with the same thing. Looks like
they are replicating. Thanks for any advice.

 

[Kevin Goodknecht]

In

Thanks guys but it didn't do the trick whenever I am on 123.com and I
try to ping the server1 I would get a reply but when I get I try
server1.123.com still no dice any other suggestion. I will tell you
that it looks like both Forward Zones are there. I can see both
123.com and abc.com in the forward zone and under that I see the
other server with the same thing. Looks like they are replicating.
Thanks for any advice.

Does nslookup resolve the FQDN?
Try:
nslookup
set d2

 

[Chirashi]

Thanks for all your help. I think I might know what the problem is. It
seems that when I create a host record on 123.com and I check ABC.com DNS I
would have 2 DNS server. first would be 123.com and then ABC.com but the
records do not match. It seems like the ABC.com has the entry on the server
but when I look at the DNS entry on ABC.com on the 123.com server. I think
replication is messed up. Is there a way I can ensure that the DNS record
is updating??? Any tools I can use. Thanks again Folks.



"Jonathan de Boyne Pollard"

 

[Jonathan de Boyne Pollard]

C> I think replication is messed up. Is there a way I can ensure
C> that the DNS record is updating???

Perform a change to the DNS database on one server. Watch for its appearance
on the other. Read the logs.