Client cant ping DNS Server by FQDN but by IP

wanderer October 20, 2010 at 08:08:05

post the results of an ipconfig /all from both the server and a workstation for review

CLIENT : Windows IP Configuration Host Name . . . . . . . . . . . . : QUAD Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet Physical Address. . . . . . . . . : 00-1D-60-73-96-30 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.191.100(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.191.1 DNS Servers . . . . . . . . . . . : 191.168.191.2 213.191.74.11 NetBIOS over Tcpip. . . . . . . . : Enabled ____________________________________________________________ SERVER : nslookup Standardserver: localhost Address: 127.0.0.1 Windows-IP-Konfiguration Hostname . . . . . . . . . . . . : s1 Primдres DNS-Suffix . . . . . . . : hasa.local Knotentyp . . . . . . . . . . . . : Unbekannt IP-Routing aktiviert . . . . . . : Nein WINS-Proxy aktiviert . . . . . . : Nein DNS-Suffixsuchliste . . . . . . . : hasa.local Ethernet-Adapter LAN-Verbindung: Verbindungsspezifisches DNS-Suffix: Beschreibung . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC Physikalische Adresse . . . . . . : 00-30-1B-48-4C-52 DHCP aktiviert . . . . . . . . . : Nein IP-Adresse. . . . . . . . . . . . : 192.168.191.2 Subnetzmaske . . . . . . . . . . : 255.255.255.0 Standardgateway . . . . . . . . . : 192.168.191.1 DNS-Server . . . . . . . . . . . : 127.0.0.1

wanderer October 20, 2010 at 12:54:47

Coming from the Unix side of the house huh? If you go to the dns logs are there errors? Do you have a host entry and ptr record for S1? I have found 127.0.0.1 isn't correct for the Microsoft world. It should work but I have found too many cases where it doesn't. You should use 192.168.191.2 for the server dns entry on the server. You will also need to go into dns server and make sure there are host and ptr records to this affect. servername host(A) 192.168.191.2 for example

Thnx for help Wanderer, - there are no errors in DNS Log, there are only events about start-up of DNS Service, no other events. - Pointer and Host entries are here and here And I changed 127.0.0.1 to 192.168.191.2 in the Server DNS Entry. Still I can ping the server by FQDN on server itselfe, but not on the client. DHCP works well. DNS doesnt work for clients.

wanderer October 20, 2010 at 14:13:27

Did you install this as a root dns server? Your dns forward lookup zone doesn't look right to me. for example my dns has in the left pane mydomain.net in the right pane I have _msdcs _sites _tcp _udp along with my NS and Host(A) records. If I expand my left pane I get the _above as well as domaindnszones forestdnszones I have no host entry here [left pane] whereas you do. All of my host and ns records are in the right pane. You have the domain and forest entries in the right pane with host entries whereas I do not. You also have under forward lookup zone left pane _msdcs.hasa.local I only have mydomain.net If you did not have dns server installed at the time of the active directly install the wizard should have created dns serve with all the correct settings. How did you do your dns setup? also please post a ipconfig /all from a workstation. Thx

OK boys and girls, if you have strange behaviour affecting DNS - DISABLE THE FIREWALL ON THE SERVER FIRST !!! Thnx for Help wanderer