The PC name ends up with DNS name appended.

  • Thread starter Thread starter mikesw
  • Start date Start date
M

mikesw

I have a local home PC net with a router to a DSL modem and the provider
is Netzero via Verizon. When I ping another computer on the home
network, the resulting FQDN name I see is pcname.dns.netzero.com.
The 'pcname' is the name of I have for my PC which is different for each one.
The "dns.netzero.com" is made up, but the router gets configured by the
ISP to be the DNS server for NetZero, lets say for discussion purposes
'dns.netzero.com'. What is happening is that the pcname is
concatenated with the dns server name and the resulting IP address I see
is the address of the DNS server not the local subnet address of 192.168.x.x
which is DHCP'd by the router. Thus, the other PC's queried/accessed by
using the "PCname" won't respond as being there since the IP address
is the dns server address. However, if I ping by the 192.168.x.x address, that
address is also valid and will respond with a reply along with now being able
to access a PC on the local subnet. I have Netbios enabled and the ipconfig
/all
shows the correct subnet address DHCP'd assigned as 192.168.x.x for a
particular
PC. I can also do filesharing too. The ipconfig also shows "broadcast" for
each
one via the registry entry of "DHCPNODETYPE" being 0x1. I don't think the
registry value should be mixed or hybrid since I don't use a Wins server nor
is
it configured. However, Ipconfig does show that the Wins proxy is enabled as
'yes'. I don't see that there is a checkbox or a way to enable the Wins Proxy
in the network card properties. Moreover, the router domain name is a blank
along with the domain name that is entered as part of network setup wizard
since
I use the Workgroup setting. Also, the registry for "domain" is empty too.
More information: all IP address' are selected to be auto from the DHCP
router,
all DNS' are auto, when I ping the pcname of the PC I'm currently logged/using
it doesn't append the dns server name and displays the correct 192.168.x.x
address.

Does anyone know how the DNS server FQDN is being appended to the local
subnet pcname?

One possibility may be that a PC was setup during network setup wizard
to connect directly to the internet vs. the others to connect to a LAN
and then to the internet? Trying to track down which one if at all this was
done to. They should all be setup to connect to the LAN and then to the
internet regardless if some are connecting to the router via wireless and
some using a CAT5 cable to the router. Hmmmmm????
 
I have a local home PC net with a router to a DSL modem and the
provider is Netzero via Verizon. When I ping another computer on
the home network, the resulting FQDN name I see is
pcname.dns.netzero.com. The 'pcname' is the name of I have for my
PC which is different for each one. The "dns.netzero.com" is made
up, but the router gets configured by the ISP to be the DNS server
for NetZero, lets say for discussion purposes 'dns.netzero.com'.
What is happening is that the pcname is concatenated with the dns
server name and the resulting IP address I see is the address of
the DNS server not the local subnet address of 192.168.x.x which
is DHCP'd by the router. Thus, the other PC's queried/accessed by
using the "PCname" won't respond as being there since the IP
address is the dns server address.
Click to expand...

Yes. It works this way. "Ping" is a TCP/IP application, not a NetBT
application. When supplied with a non-qualified domain name (one
without dots), TCP appends domain names according to how TCP/IP was
configured. In your case, if you go to:
Network Control Panel -> Double-click connection -> Properties ->
double-click "Internet Protocol" in window -> Advanced -> Dns Tab ->
You probably have "Append primary and connection-specific DNS Suffixes
checked. The suffixes you are seeing are provided by your ISP as part
of the DHCP configuration. This is actually needed, for example, when
your ISP tells you to configure your Email Client Server with simply
"mail", knowing that the appropriate suffix will automatically be
appended depending on what part of the country you are in.

If the resulting DNS name does not resolve, then Windows will fall back
on Windows Networking to resolve the name. If it does resolve, then
you have an IP address of a computer that you don't want.
However, if I ping by the 192.168.x.x address, that address is
also valid and will respond with a reply along with now being able
to access a PC on the local subnet.
Click to expand...

Yes. In this case, you've eliminated the middleman name-resolving step
and called out the address manually.
I have Netbios enabled and the ipconfig /all shows the correct
subnet address DHCP'd assigned as 192.168.x.x for a particular PC.
I can also do filesharing too. The ipconfig also shows "broadcast"
for each one via the registry entry of "DHCPNODETYPE" being 0x1. I
don't think the registry value should be mixed or hybrid since I
don't use a Wins server nor is it configured.
Click to expand...

If you configure a WINS server, the type will default to Hybrid. If you
don't, it will probably default to "Broadcast". Both Hybrid and
Broadcast will do broadcasts if the WINS server does not resolve.
However, Ipconfig does show that the Wins proxy is enabled as
'yes'. I don't see that there is a checkbox or a way to enable the
Wins Proxy in the network card properties.
Click to expand...

Since you don't seem to be using a WINS server, the proxy function will
not do anything. How to enable/disable the proxy function is shown
here:
Moreover, the router domain name is a blank along with the domain
name that is entered as part of network setup wizard since I use
the Workgroup setting. Also, the registry for "domain" is empty
too. More information: all IP address' are selected to be auto
from the DHCP router, all DNS' are auto,
Click to expand...

Don't confuse a TCP/IP domain name (the one provided by your ISP that
get appended to a non-FQDN) with the Domain/Workgroup names that are
associated with NetBT (Windows Networking) protocol. Two different
things.
when I ping the pcname of the PC I'm currently logged/using it
doesn't append the dns server name and displays the correct
192.168.x.x address.
Click to expand...

Your PC name is Cached locally and apparently is resolved before an
external DNS query occurs.
Does anyone know how the DNS server FQDN is being appended to the
local subnet pcname?
Click to expand...

Answered above. (It is configured that way)
One possibility may be that a PC was setup during network setup
wizard to connect directly to the internet vs. the others to
connect to a LAN and then to the internet? Trying to track down
which one if at all this was done to. They should all be setup to
connect to the LAN and then to the internet regardless if some are
connecting to the router via wireless and some using a CAT5 cable
to the router. Hmmmmm????
Click to expand...

Gibberish. When a wireless router is handling network traffic, all
traffic, whether wireless or wired, gets around the same way. When
communicating with a device on the same network, the traffic goes
directly to that device, wireless or wired as is appropriate. All
internet traffic is sent through the Router's WAN port.

I don't know what your problem is... Everything is working as it
should. You do seem to be confusing normal TCP/IP protocols with
Windows Networking's NetBT protocols (NetBT = NetBIOS-over-TCP/IP).
Windows Networking has different name resolving techniques than
straight TCP/IP (Using Master Browsers and "LMHosts" file instead of
DNS Servers and "Hosts" file) although when desperate, they tend to
query each other's tables.

A good place to look to resolve this confusion is:
"Domain Browsing with TCP/IP and LMHOSTS Files"
<http://support.microsoft.com/kb/150800>

HTH,
John
 
On the computer, look at the DNS page of the TCP/IP properties for the LAN
connection. Chances are you have a 'DNS suffix' set, and possibly also a
'DNS search order.' On an internal LAN these items should be blank UNLESS you
own a domain for internal use, such as a large company might have.

Having the name of a domain which you do not own -and which is external to
your LAN- in here will cause trouble with connections between local
computers.

Before removing the suffix entry, you may wish to check the server settings
in your mail client, as these may be relying on the domain being appended to
a short-form name. If so, change the mailserver names accordingly.
 
Back
Top