|
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Ok I will try best to explain.
Lets say my DNS server is name "A" I have another server is named "B" I am at server B I try to ping at the command promt using "Ping A" and it works fine. I then try "Ping domain.local" and it works fine. I then try "Ping A.domain.Local" and it does not work. What would be causing this problem? |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
Ok update.
I am not able to ping domain.local now. I have the DNS set on server b to server a. I can ping server a from server b with both IP addres and computer name. I have looked into server a dns setting and it has all the A records. I can ping domain.local from server a. I can ping all computer from server a in format computer.domain.local. Any ideas? "Josh" wrote: > Ok I will try best to explain. > Lets say my DNS server is name "A" > I have another server is named "B" > > I am at server B I try to ping at the command promt using "Ping A" and it > works fine. I then try "Ping domain.local" and it works fine. I then try > "Ping A.domain.Local" and it does not work. What would be causing this > problem? |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
>> Ok I will try best to explain.
>> Lets say my DNS server is name "A" >> I have another server is named "B" >> >> I am at server B I try to ping at the command promt using "Ping A" and it >> works fine. I then try "Ping domain.local" and it works fine. I then try >> "Ping A.domain.Local" and it does not work. What would be causing this >> problem? Several possibilities occur: Simplest would be if the machines are NOT in "domain.local" (the DNS zone) but some other zone. Zones (or Domain) for every machine should be set in the SYSTEM CONTROL Panel and they need to be registered in your DNS zones. Usually they will self-register (dynamically) in Windows but YOU must choose to set the zone to allow dynamic resolution OR you must manually register them. Second is that the resolution is actually occurring through NetBIOS (either a broadcast -- only on same subnet -- or by using WINS.) The situations (failure to register and succeeding by using NetBIOS) may be intertwined. > Ok update. > > I am not able to ping domain.local now. > I have the DNS set on server b to server a. Correct. > I can ping server a from server b with both IP addres and computer name. Server A should generally be set to the same "client DNS" settings as B. It should point to itself (or other INTERNAL DNS servers) STRICTLY. > I have looked into server a dns setting and it has all the A records. > I can ping domain.local from server a. I can ping all computer from server > a > in format computer.domain.local. Any ideas? You are giving inconsistent reports or highly confusing reports. Go check the DNS records and make sure both servers are registered properly. Use NSLookup to PROVE you can resolve AND be SPECIFIC in using the DNS server (A?) nslookup ServerA IP.DNS.Server.A nslookup ServerB IP.DNS.Server.A (do all of these from EACH server) nslookup ServerA.domain.local IP.DNS.Server.A nslookup ServerB.domain.local IP.DNS.Server.A (do all of these from EACH server) Record each command and actual results (ignore any errors about failure to resolve the DNS server IP back to its name -- pay attention only to the actual answer to each question.) If the full name fails while the partial name works, then this is due to failure to correctly name the local machine in the SYSTEM CONTROL panel (or a related suffix issue.) Also post your full "Ipconfig /all" from both machines. (Clearly label which is A and B) Do not "type" this in or use a graphic screen capture but rather send the actual output to a text file (e.g., >configA.txt ) and do not edit the results but post it in total. > "Josh" wrote: > -- Herb Martin, MCSE, MVP Accelerated MCSE http://www.LearnQuick.Com [phone number on web site] |
|
![]() |
| Outils de la discussion | |
|
|