Pinging Host Names as opposed to pinging FQDNs



  • 1. [Newbie] including Linux server in DNS
    Hi all. A customer has a small LAN with a W2k AD DC. A new box is soon going to be added to the network, and it will be an FTP server, based on Linux OS. I would like all workstations on the network to be able to reach the server typing (which is by the way, the address used by my customer's customers to reach the server from the internet, and is therefore known on the web with an external IP address). Of course I'd like to do that without adding a line to all hosts files in the LAN, so I thought the DC's DNS would handle this, pointing workstations to the internal IP address. I turned to the W2K server's admin who told me it's not possible, "because the domain handled by the DC is not, but someothername.someotherextension" Is this correct? I think it's unbelievable. Please remember that the Linux box cannot participate in the AD domain (of course). Thanks for any input Stefano
  • 2. XP clients registering unauthorized "Same as Parent" record
    Hello, I've been combing the Web trying to figure this one out, but I'm stumped. Our large multi-site network has a root domain and two child domains, with a total of 14 domain controllers. Each separate location has a DNS server that is configured as a slave to the primary internal DNS that runs on one of the DCs for the root domain. Everything works great, except that periodically we start having logon problems and - almost invariably - the difficulty is that an XP machine has registered itself (or been registered) with a "Same as Parent" record in DNS, resulting in some requests for the root domain going unanswered. I initially thought it might be an issue related to defining workgroup/domain membership after re-imaging a machine, but just this week it happened with a machine that's been stable for nearly a year. I'm stumped... anyone have any insight?
  • 3. Importing mass amounts of users from a database to active director
    Hi can anyone help I need a way to import 600 users form a Microsoft Access database to active directory. Thanks Nigel
  • 4. Proper DNS setup with two domains - How?
    I have a DHCP server on our network that issues addressd and DNS server addresses to all workstations. The problem (for me) is that I have two domains each with their own primary DNS. I have two issues I need to understand: 1) Since I will be sharing resourses between domains both domains need to know about each other. How do I make sure Domain A knows about computers in Domain B? 2) I would like the DHCP server to set the proper Primary DNS server for Domain A and Domain B according to their primary AD servers (e.g. Domain A's primary DNS server is it's own AD server and same for Domain B) Both LANs are running WIndows 2000 server with Active Directory. Domain B's AD server is acting as the DHCP server. Any help is appreciated! -Fran-

Re: Pinging Host Names as opposed to pinging FQDNs

Postby Herb Martin » Tue, 12 Aug 2003 01:13:25 GMT


Yes.  DNS and/or WINS server(s) setup correctly do this
quite easily.

Ok, so both zones are at both sites (Srv A & B each have both)
pinging by name should work just fine IF pinging by number already
works (you did register the names, right?)

Technically it's not a FQDN until you put a DOT. on the END., e.g.,
www.Domain.Com.  <-- DOT there (but lots of people use FQDN
to MEAN a multipart name with several tags ending in a TLD

Host name is not a definitive term, it is commonly just a synonym
for what you are calling a FQDN.

Your machine can ping by just the machine part IF the other machine is in
your machines SAME Domain/Zone OR you add an additional suffix
search list in the NIC properties -- notice this is dependent on being
able to ping by the full name which is dependent on the IP address

Finally, if you wish to use NetBIOS names (like in the Browser)
then you might need WINS -- especially to get the browser to
work across subnets and across domains.

WINS server at each location, local clients use the local WINS
server (clients INCLUDE the WINS server and other servers,
especially DCs), then the two WINS server must be set to

Re: Pinging Host Names as opposed to pinging FQDNs

Postby Bryan Blair » Tue, 12 Aug 2003 22:13:23 GMT

I added the Domain Name for DNS Server A in the Suffix tab under TCP
properties for a workstation in the opposite Domain and was able to ping the
corresponding Host name!!!

I also set up replication to take place between the two primary WINS servers
in Domain A and B.  However, I waited a while and still did not see the
Domain A appear in the Network Places of a workstation in Domain B.  Does
this replication take a long time?


Re: Pinging Host Names as opposed to pinging FQDNs

Postby Herb Martin » Wed, 13 Aug 2003 00:21:54 GMT


Cool.  See what happens in DNS is the "single name" is
insufficient.  So when you type a bare name like that it's
going to fail -- BUT it works because the resolver sticks
Domain.Com (whatever) on the end.

Two more choices exist for this "auto suffixing":
        checking parent domains (check box in NIC\IP DNS too)
        extra suffixes in the NIC properties (You used that.)
Parent domains/zones work by removing the left-most tag
from the machine's domain-part and trying (each) that.
So if a machine is in a deep tree, e.g.,


First it tries the full name, then it would drop grand, then child.
I have never checked to see if it will try "" though.
Then it would check the suffixes listed.  Never list the domain
itself as a suffix (it might check twice and we know it won't
help) -- never list a parent domain in 'extra' IF you also told
it to check parents.


You set the schedule right there in the MMC for the replication partner.
Did you remember to go both ways?  (I think that's the default these
What schedule did you SELECT?

Some people mistakenly believe that "delaying replication" reduces the
load on their WAN -- this is not generally true.  Ok, maybe a touch,
but not by much usually.

If you replicate each hour verses ever 12 hours, then you send about
1/12 of the 12 hour replication each hour -- it's about the same amount
overall and the "little" replications are likely less noticable than 10
the size.

Of course, there is some overhead just to set it up each time and if the
same records get updated many times (especially to the same values)
there is little reason to keep sending redundant data (like someone
boots their macine twice an hour).  Generally these contributions to
replication size are small.

You can force replication from the WINS MMC GUI.
You can also "connect" to the other server from the single MMC
and that might prove you have IP working between them.

Re: Pinging Host Names as opposed to pinging FQDNs

Postby Bryan Blair » Wed, 13 Aug 2003 01:02:04 GMT

After waiting a little bit longer replication took place......Everything is
working fine now!!  Thanks for the advice!!


Similar Threads:

1.Strange network problems - pings to host are fine, pings from host fail

Sorry for the long post - I've tried to outline the symptoms of my 
problem, and what I've tried to fix it.

I'm having some networking problems with a PC running an old version of 
Red Hat (kernel 2.2).  The PC came with a machine we have bought 
second-hand - as far as I know, everything was working before the 
machine was moved to our company.

To keep things simple, we have the Red Hat machine connected to a 
Windows XP machine that came with it, with only a simple switch in 
between.  Each machine is set up with a fixed IP address on the same 

 From the XP machine, I can ping the Red Hat machine reliably and 
quickly.  From the Red Hat machine, pings to the XP machine /generally/ 
fail - typically there are about 80%-90% failures.  Those pings that 
don't fail, are fast (reply time about 1 ms).  On the XP machine, it's 
easy to see the packet counters showing packets in and replies out.  On 
the Red Hat machine, ifconfig shows similar packet rx and tx counts, and 
zero error counts.

arping to the XP machine from the Red Hat machine is reliable and fast.

When we try a browser on the XP machine and address the web server on 
the Red Hat host, there is generally a long pause (perhaps minutes), 
then suddenly the page appears.

We have tried using another Linux box in place of the original XP 
machine, with the same results from the Red Hat system.

We have tried replacing the cables and switch, with no effect - given 
that arpings are working perfectly it's hard to see how it could be a 
hardware problem.

I'm not very familiar with Red Hat or a 2.2 kernel (my experience is 
mostly with Debian and related distros, and with 2.4 and 2.6 kernels). 
But "ipchains -L" shows no firewalling (everything accepted), "ifconfig" 
and "route -n" have the expected setup, and I could not stop anything 
unexpected with "sysctrl".

One of my colleagues will try a different network card this evening.

Any ideas or tips would be much appreciated.  We've tried pretty much 
every sensible idea we can think of, so I'm ready to listen to any crazy 
or unlikely tricks.



2.Can ping on both ip and host name but nbtstat -a gets "host not found"

We have 2 servers with NT4 that we are trying to install Symantec antivirus 8,1 with another server as parent server and it fails because the server can not be found
Doing a Ping from the server that we are trying to install on works fine on both IPadress and host name but trying to do a nbtstat -a ends up with a "host not found !!
All IP-configurations are correct on both servers and is the same as all our servers where we had no problems doing the SAV installation
I dont have a clue what causes this and i wonder if someone else has an idea


3.Ping not pinging name

4.can ping by IP, cannot ping by name

After one of our employess left work we found that we cannot ping his
We can ping it by ip-address, not by the servername.
We can connect to it remote only by ip-address not by servername.



5.cannot ping server name, can ping ip address

Running SBS2003 and suddenly, my pc's will not sync with server. I cannot 
ping server name, but I can ping IP address. In mapped network drives, I can 
disconnect network, change name to IP address, can see file, but still cannot 
Thanks in advance.

6. Can ping IP Address but cant ping name

7. Ping IP is ok, but can not ping by name

8. Can't ping dns name but can ping ip

Return to Windows


Who is online

Users browsing this forum: No registered users and 57 guest