Can resolve by hostname, but not with FQDN (internal and external)

We've a SBS 2003 server that can't resolve to internal and external FQDN, but
there is no problem to resolve internal hostnames.

Also, nslookup works fine. But a ping to an external server doesn't work.
The hosts is not changed.

-----------

C:\>nslookup www.google.com
Server: sbs01.domain.local
Address: 10.0.0.10

Non-authoritative answer:
Name: www.l.google.com
Addresses: 74.125.77.104, 74.125.77.103, 74.125.77.147, 74.125.77.99
Aliases: www.google.com

-----------

Right after the nslookup i do a ping to www.google.com with the following
result:

C:\>ping www.google.com
Ping request could not find host www.google.com. Please check the name and
try again.

-----------

Windows IP Configuration
Host Name . . . . . . . . . . . . : sbs01
Primary Dns Suffix . . . . . . . : domain.local

Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.local

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . : domain.local

Description . . . . . . . . . . . : HP Network Team #1
Physical Address. . . . . . . . . : 00-1B-78-39-32-74
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 10.0.0.10
Primary WINS Server . . . . . . . : 10.0.0.10

-----------

Ping results to internal hostname:

C:\>ping app01

Pinging app01 [10.0.0.11] with 32 bytes of data:

Reply from 10.0.0.11: bytes=32 time<1ms TTL=128
Reply from 10.0.0.11: bytes=32 time<1ms TTL=128
Reply from 10.0.0.11: bytes=32 time<1ms TTL=128
Reply from 10.0.0.11: bytes=32 time<1ms TTL=128

Ping statistics for 10.0.0.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

-----------

and to the internal FQDN:

C:\>ping app01.domain.local
Ping request could not find host app01.domain.local. Please check the name
and try again.

-----------

C:\>route print

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 1b 78 39 32 74 ...... HP Network Team #1
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.10 10
10.0.0.0 255.255.255.0 10.0.0.10 10.0.0.10 10
10.0.0.10 255.255.255.255 127.0.0.1 127.0.0.1 10
10.255.255.255 255.255.255.255 10.0.0.10 10.0.0.10 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 10.0.0.10 10.0.0.10 10
255.255.255.255 255.255.255.255 10.0.0.10 10.0.0.10 1
Default Gateway: 10.0.0.1
===========================================================================
Persistent Routes:
None

In news:077A0867-9F99-48F5-BB6A-797407FD471B@microsoft.com,
Foes <Foes@discussions.microsoft.com>, posted the following:
> We've a SBS 2003 server that can't resolve to internal and external
> FQDN, but there is no problem to resolve internal hostnames.
>
> Also, nslookup works fine. But a ping to an external server doesn't
> work. The hosts is not changed.
>
> -----------
>
> C:\>nslookup www.google.com
> Server: sbs01.domain.local
> Address: 10.0.0.10
>
> Non-authoritative answer:
> Name: www.l.google.com
> Addresses: 74.125.77.104, 74.125.77.103, 74.125.77.147, 74.125.77.99
> Aliases: www.google.com
>
> -----------
>
> Right after the nslookup i do a ping to www.google.com with the
> following result:
>
> C:\>ping www.google.com
> Ping request could not find host www.google.com. Please check the
> name and try again.
>
> -----------
>
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : sbs01
> Primary Dns Suffix . . . . . . . : domain.local
>
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : domain.local
>
> Ethernet adapter Server Local Area Connection:
>
> Connection-specific DNS Suffix . : domain.local
>
> Description . . . . . . . . . . . : HP Network Team #1
> Physical Address. . . . . . . . . : 00-1B-78-39-32-74
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 10.0.0.10
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 10.0.0.1
> DNS Servers . . . . . . . . . . . : 10.0.0.10
> Primary WINS Server . . . . . . . : 10.0.0.10
>
> -----------
>
> Ping results to internal hostname:
>
> C:\>ping app01
>
> Pinging app01 [10.0.0.11] with 32 bytes of data:
>
> Reply from 10.0.0.11: bytes=32 time<1ms TTL=128
> Reply from 10.0.0.11: bytes=32 time<1ms TTL=128
> Reply from 10.0.0.11: bytes=32 time<1ms TTL=128
> Reply from 10.0.0.11: bytes=32 time<1ms TTL=128
>
> Ping statistics for 10.0.0.11:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> -----------
>
> and to the internal FQDN:
>
> C:\>ping app01.domain.local
> Ping request could not find host app01.domain.local. Please check the
> name and try again.
>
> -----------
>
> C:\>route print
>
> IPv4 Route Table
> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10003 ...00 1b 78 39 32 74 ...... HP Network Team #1
> ===========================================================================
> ===========================================================================
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> 0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.10
> 10
> 10.0.0.0 255.255.255.0 10.0.0.10 10.0.0.10
> 10
> 10.0.0.10 255.255.255.255 127.0.0.1 127.0.0.1
> 10
> 10.255.255.255 255.255.255.255 10.0.0.10 10.0.0.10
> 10 127.0.0.0 255.0.0.0 127.0.0.1
> 127.0.0.1 1 224.0.0.0 240.0.0.0 10.0.0.10
> 10.0.0.10 10 255.255.255.255 255.255.255.255 10.0.0.10
> 10.0.0.10 1 Default Gateway: 10.0.0.1
> ===========================================================================
> Persistent Routes:
> None





Are any services disabled, such as the DHCP Client service?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
aceman@mvps.RemoveThisPart.org

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

In news:077A0867-9F99-48F5-BB6A-797407FD471B@microsoft.com,
Foes <Foes@discussions.microsoft.com>, posted the following:
> We've a SBS 2003 server that can't resolve to internal and external
> FQDN, but there is no problem to resolve internal hostnames.
>
> Also, nslookup works fine. But a ping to an external server doesn't
> work. The hosts is not changed.

I also forgot to ask, does the Root zone exist under Forward Lookup Zones in
DNS? The Root zone looks like a period (".") under the zone.

In addition, just to point out, nslookup has its own internal resolver
service independent of the operating system, whereas ping uses the operating
system's resolver service. That was why I had asked about the DHCP Client
service. Somewhat of a misnomer, whether the machine is set to DHCP or not,
it is the machine's resolver and DNS registration service. If it is
disabled, pings and other resolutions dependent on the operating system
resolver will not work.

Ace

"Ace Fekay [Microsoft Certified Trainer]" wrote:

> In news:077A0867-9F99-48F5-BB6A-797407FD471B@microsoft.com,
> Foes <Foes@discussions.microsoft.com>, posted the following:
> > We've a SBS 2003 server that can't resolve to internal and external
> > FQDN, but there is no problem to resolve internal hostnames.
> >
> > Also, nslookup works fine. But a ping to an external server doesn't
> > work. The hosts is not changed.
>
> I also forgot to ask, does the Root zone exist under Forward Lookup Zones in
> DNS? The Root zone looks like a period (".") under the zone.
>
> In addition, just to point out, nslookup has its own internal resolver
> service independent of the operating system, whereas ping uses the operating
> system's resolver service. That was why I had asked about the DHCP Client
> service. Somewhat of a misnomer, whether the machine is set to DHCP or not,
> it is the machine's resolver and DNS registration service. If it is
> disabled, pings and other resolutions dependent on the operating system
> resolver will not work.
>
> Ace
>

Thanks for the reply. But all services are running on the server. I've also
runned netstat and dcdiag now, here are the results:

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SBS01
Starting test: Connectivity
The host 356b3426-f914-4784-8408-bc940bda5003._msdcs.domain.local
could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(356b3426-f914-4784-8408-bc940bda5003._msdcs.domain.local)

couldn't be resolved, the server name (sbs01.domain.local)

resolved to the IP address (10.0.0.10) and was pingable. Check that

the IP address is registered correctly with the DNS server.
......................... SBS01 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SBS01
Skipping all tests, because server SBS01 is
not responding to directory service requests

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : VOS-CAPELLE
Starting test: CrossRefValidation
......................... VOS-CAPELLE passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... VOS-CAPELLE passed test CheckSDRefDom

Running enterprise tests on : domain.local
Starting test: Intersite
......................... domain.local passed test Intersite
Starting test: FsmoCheck
......................... domain.local passed test FsmoCheck


----------------------------------
NETDIAG:

Computer Name: SBS01
DNS Host Name: sbs01.domain.local
System info : Microsoft Windows Server 2003 (Build 3790)
Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
List of installed hotfixes :
KB924667-v2
KB925398_WMP64
KB925876
KB925902-v2
KB927891
KB929123
KB930178
KB932168
KB933714
KB933729
KB933854
KB935839
KB935840
KB936357
KB936782
KB938127
KB938464
KB941569
KB942830
KB942831
KB943055
KB943460
KB943485
KB943729
KB944338-v2
KB944653
KB945553
KB946026
KB948496
KB948745
KB949014
KB950762
KB950974
KB951066
KB951698
KB951748
KB952069
KB952954
KB954211
KB954600
KB955069
KB955839
KB956391
KB956802
KB956803
KB956841
KB957097
KB958215
KB958644
KB958687
KB960714
Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Server Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : sbs01.domain.local
IP Address . . . . . . . . : 10.0.0.10
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 10.0.0.1
Primary WINS Server. . . . : 10.0.0.10
Dns Servers. . . . . . . . : 10.0.0.10


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.

WINS service test. . . . . : Passed


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{52CA75BD-167E-4AA6-B09C-D168A9C14446}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the
name
'sbs01.domain.local.'. [WSAENOPROTOOPT ]
The name 'sbs01.domain.local.' may not be registered in DNS.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS server '10.0.0.10'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{52CA75BD-167E-4AA6-B09C-D168A9C14446}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{52CA75BD-167E-4AA6-B09C-D168A9C14446}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

------------------------------------

Any other ideas?

"Foes" <Foes@discussions.microsoft.com> wrote in message
news:E79D14FC-483C-4711-A803-DA884FB36484@microsoft.com...
> "Ace Fekay [Microsoft Certified Trainer]" wrote:
>
>> In news:077A0867-9F99-48F5-BB6A-797407FD471B@microsoft.com,
>> Foes <Foes@discussions.microsoft.com>, posted the following:
>> > We've a SBS 2003 server that can't resolve to internal and external
>> > FQDN, but there is no problem to resolve internal hostnames.
>> >
>> > Also, nslookup works fine. But a ping to an external server doesn't
>> > work. The hosts is not changed.
>>
>> I also forgot to ask, does the Root zone exist under Forward Lookup Zones
>> in
>> DNS? The Root zone looks like a period (".") under the zone.
>>
>> In addition, just to point out, nslookup has its own internal resolver
>> service independent of the operating system, whereas ping uses the
>> operating
>> system's resolver service. That was why I had asked about the DHCP Client
>> service. Somewhat of a misnomer, whether the machine is set to DHCP or
>> not,
>> it is the machine's resolver and DNS registration service. If it is
>> disabled, pings and other resolutions dependent on the operating system
>> resolver will not work.
>>
>> Ace
>>
>
> Thanks for the reply. But all services are running on the server. I've
> also
> runned netstat and dcdiag now, here are the results:
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\SBS01
> Starting test: Connectivity
> The host 356b3426-f914-4784-8408-bc940bda5003._msdcs.domain.local
> could not be resolved to an
> IP address. Check the DNS server, DHCP, server name, etc
> Although the Guid DNS name
>
> (356b3426-f914-4784-8408-bc940bda5003._msdcs.domain.local)
>
> couldn't be resolved, the server name (sbs01.domain.local)


Does the following record, which stated in the dcdiag that it was not
resolvable, exist in DNS?
(356b3426-f914-4784-8408-bc940bda5003._msdcs.domain.local)
If so, what does it point to?

Does the Primary DNS Suffix on the DC match the zone name in DNS?

Under the zone's properties, Nameservers tab, does this DC show up?

What errors are in the event logs?

If the zone is AD integrated, and if AD is having problems, then DNS will
not be able to load the zone.

Ace