Appending domain to ping issues

  • Thread starter Thread starter Hank
  • Start date Start date
ok, Here Goes:
/////////////////Entire HOSTS File///////////////////////
127.0.0.1 localhost
192.168.100.25 this.sucks
192.168.100.25 doh
/////////////////////////////////////////////////////////

Caches have been cleared and machines rebooted. [Client/DNSServer]
******************************************************************
ping this.sucks (( or ping this.sucks. ))
Pinging this.sucks.courthouseinternal.net [64.94.110.11] ....
Request Timed Out.
....
....
******************************************************************
******************************************************************
ping doh
Pinging doh [192.168.100.25]...
reply....
reply....
etc
******************************************************************

Now onto DNS based Queries: my .Dev zone worked fine for months
before all this happened on Monday

******************************************************************
ping hank.dev (( or ping hank.dev. ))
Pinging hank.dev.courthouseinternal.net [64.94.110.11]...
Request timed out.
Request ....
etc.....
******************************************************************

nslookup hank.dev

Server: courthouseplaza.courthouseinternal.net
Address: 192.168.100.4

Name: hank.dev
Address: 192.168.100.25

******************************************************************

It looks like my hosts file isn't working, and the pings are degrading
to append our root domain to the address.

Any ideas?
 
What version of windows is this?

--
William Stacey, DNS MVP

Hank said:
ok, Here Goes:
/////////////////Entire HOSTS File///////////////////////
127.0.0.1 localhost
192.168.100.25 this.sucks
192.168.100.25 doh
/////////////////////////////////////////////////////////

Caches have been cleared and machines rebooted. [Client/DNSServer]
******************************************************************
ping this.sucks (( or ping this.sucks. ))
Pinging this.sucks.courthouseinternal.net [64.94.110.11] ....
Request Timed Out.
...
...
******************************************************************
******************************************************************
ping doh
Pinging doh [192.168.100.25]...
reply....
reply....
etc
******************************************************************

Now onto DNS based Queries: my .Dev zone worked fine for months
before all this happened on Monday

******************************************************************
ping hank.dev (( or ping hank.dev. ))
Pinging hank.dev.courthouseinternal.net [64.94.110.11]...
Request timed out.
Request ....
etc.....
******************************************************************

nslookup hank.dev

Server: courthouseplaza.courthouseinternal.net
Address: 192.168.100.4

Name: hank.dev
Address: 192.168.100.25

******************************************************************

It looks like my hosts file isn't working, and the pings are degrading
to append our root domain to the address.

Any ideas?



"William Stacey" <[email protected]> wrote in message
1) hosts file should be used. clear the cache on the machine with ipconfig
/flushdns and clear the cache on the dns server using ui or dnscmd
/clearcache and try again.
2) Lets focus on one client and the dns server for now. Show me the command
your using that is not returning right (i.e. ping, nslookup, dig). From the
client use nslookup or dig to make sure a directed query returns the answer
you seek.
3) Did you try it with the "." dot on the end?

--
William Stacey, DNS MVP


did
not
Click to expand...
Click to expand...
 
I had the same systoms and here is what i did.

We are a small company that uses DHCP but this Verisign
deal really screwed things up. I don't know if this is
the correct answer but i was able to solve this issue. I
currently run a W2K server with AD, DNS and DHCP on the
same server. I added the IP of my W2K server to my DHCP
DNS scope option and made sure it was first in the list.
Rebooted all machines and solved the issue for the time
being.

Bill
-----Original Message-----
ok, Here Goes:
/////////////////Entire HOSTS File///////////////////////
127.0.0.1 localhost
192.168.100.25 this.sucks
192.168.100.25 doh
/////////////////////////////////////////////////////////

Caches have been cleared and machines rebooted. [Client/DNSServer]
*********************************************************
Click to expand...
*********
ping this.sucks (( or ping this.sucks. ))
Pinging this.sucks.courthouseinternal.net [64.94.110.11] ....
Request Timed Out.
....
....
********************************************************* *********
*********************************************************
Click to expand...
*********
ping doh
Pinging doh [192.168.100.25]...
reply....
reply....
etc
********************************************************* *********

Now onto DNS based Queries: my .Dev zone worked fine for months
before all this happened on Monday

********************************************************* *********
ping hank.dev (( or ping hank.dev. ))
Pinging hank.dev.courthouseinternal.net [64.94.110.11]...
Request timed out.
Request ....
etc.....
********************************************************* *********

nslookup hank.dev

Server: courthouseplaza.courthouseinternal.net
Address: 192.168.100.4

Name: hank.dev
Address: 192.168.100.25

********************************************************* *********

It looks like my hosts file isn't working, and the pings are degrading
to append our root domain to the address.

Any ideas?



"William Stacey" <[email protected]> wrote in message
1) hosts file should be used. clear the cache on the machine with ipconfig
/flushdns and clear the cache on the dns server using ui or dnscmd
/clearcache and try again.
2) Lets focus on one client and the dns server for now. Show me the command
your using that is not returning right (i.e. ping, nslookup, dig). From the
client use nslookup or dig to make sure a directed query returns the answer
you seek.
3) Did you try it with the "." dot on the end?

--
William Stacey, DNS MVP


other stuff Verisign did
not
Click to expand...
Click to expand...
<PleaseSubstituteMyActualFirstName&[email protected]
m> wrote in
 
H> my .Dev zone worked fine for months
H> before all this happened on Monday

Your "dev." "zone" _still_ "works fine". The problem is that a
"courthouseinternal.net." domain has, thanks to Verisign's land grab,
suddenly sprung into existence in the public DNS database, where it
didn't exist before. Your DNS Client's search path is causing the
subdomains of that name to be queried before any others. (A while
back I said in this very forum that search paths are a menace. The
sudden appearance of an unexpected name->address mapping like this is
one of the very reasons why.)

You've set up "split horizon" DNS service, pruning the DNS namespace
tree at "courthouseinternal.net." and grafting on your own data for
that domain and all of its subdomains. But somehow you haven't done
it properly, because lookups for subdomains of that name are still
yielding the results from the public DNS database. Does your DNS
server at 192.168.100.4 answer queries for "*.courthouseinternal.net."
domain names with the intended, internal view, results ? Is that
the DNS server that your individual DNS Clients have been configured
to talk to ?

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-split-horizon.html>
 
If I ping "Hank" I resolve to hank.CourtHouseInternal.net and ping it
properly, if I ping "hank.CourtHouseInternal.net" I get sent out to
verisign's ip. Very puzzling

All my internal clients are configured to use only the internal dns.

The box that I am working from is w2k server.
 
In
Hank said:
If I ping "Hank" I resolve to hank.CourtHouseInternal.net and ping it
properly, if I ping "hank.CourtHouseInternal.net" I get sent out to
verisign's ip. Very puzzling

All my internal clients are configured to use only the internal dns.

The box that I am working from is w2k server.
Click to expand...


If it get's Verisign's IP, then it means that it doesn;t believe the zone is
correctly configured on your server or misspelled or something to that
effect. If Verisign didn't make the change, then you would have probably got
"can't find host" message.

Do you have forwarding set on your internal DNS?
Secure Cache Against Pollution set?
Did you disable recursion under Forwarding tab?

When testing it, clear the cache first on the server and client and try
again or in between ping tests.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
H> If I ping "Hank" I resolve to hank.CourtHouseInternal.net and
H> ping it properly, if I ping "hank.CourtHouseInternal.net" I
H> get sent out to verisign's ip. Very puzzling

Not totally, though. That seems to be the search path issue still.
The fact that a domain name contains multiple labels does not make
it a fully qualified domain name. Try again, this time using a
fully qualified domain name.

<URL:http://www.menandmice.com/online_docs_and_faq/glossary/fqdn.htm>

H> All my internal clients are configured to use only the internal dns.

Good. Now: What is the response received when you send an "A"
query for "hank.courthouseinternal.net." to your DNS server at
192.168.100.4 (using a DNS diagnosis tool, such as "dig",
"dnsquery", or "host") ?
 
Back
Top