• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 277
  • Last Modified:

DNS error

We have set up *.*.gov.* *.*.*.99 as intranet website on one of our netstaging web servers. http:\\.* *.*.*.99 brings up the web site in the browser. http:\\*.*.gov.* returns dns error. I have created a primary zone in Forward Lookup Zone callled *.gov.* and have also created Host (A) called * with the data being .* *.*.*.99 in the primary zone.Update associated pointer (PTR) record is
checked. Have not done anything with Reverse look up zones yet
C:\>nslookup *.*.gov.*
Server: *.*.network
Address:  *.*.*.81
Name:    *.*.gov.*
Address:  .* *.*.*.99
Problem: http:\\*.*.gov.* does not come up (the page cannot be displayed error) while http://*.*.*.99/ does bring the site.
What's going wrong or what else needs to be done - thanks
0
kumali
Asked:
kumali
  • 6
  • 5
2 Solutions
 
debuggerauCommented:
what happens when you ping the DNS address?
0
 
kumaliAuthor Commented:
C:\>ping .* *.*.*.99
Pinging .* *.*.*.99 with 32 bytes of data:
Reply from .* *.*.*.99 : bytes=32 time<1ms TTL=127
Reply from .* *.*.*.99 : bytes=32 time<1ms TTL=127

C:\>ping -a .* *.*.*.99
Pinging .* *.*.*.99 with 32 bytes of data:
Reply from .* *.*.*.99 : bytes=32 time<1ms TTL=127
Reply from .* *.*.*.99 : bytes=32 time<1ms TTL=127
0
 
mikey1hCommented:
ok     from here I Am showing agimo.....   to resolve to 208.69.32.132 on nslookup and ping.

check your name registrar to make sure the name servers are pointed to you DNS server, and double check the DNS server....    if you are behind a router, and using server 2003, AD has issues with arbitratily changing DNS records to the internal ip address assigned to the NIC.   if this is the case, you will still point DNS to your static IP, and set up port forwarding in the router
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
debuggerauCommented:
that ping is to the IP address, not the DNS address..

try:

ping *.*.gov.*
0
 
kumaliAuthor Commented:
C:\>ping *.*.gov.*
Pinging *.*.gov.* [.* *.*.*.99 ] with 32 bytes of data:
Reply from .* *.*.*.99 : bytes=32 time<1ms TTL=127
Reply from .* *.*.*.99 : bytes=32 time<1ms TTL=127
0
 
debuggerauCommented:
Ok, that's good, so you can resolve and communicate to that address..

so there should be no difference, unless the browser uses a proxy which is not aware of that address..
0
 
kumaliAuthor Commented:
We do use Proxly, the exclusion list contains *.198.*; so it should work but does not. I got a ptr entry in the reverse look up zone as well (manually created). However if i include ;*.*gov.country in the exclusion list it works. Is that the solution?
0
 
debuggerauCommented:
it will be if you wanted to remain with the proxy...
0
 
kumaliAuthor Commented:
thank you, this has been sorted out now
0
 
debuggerauCommented:
for the record, what actually did it?
0
 
kumaliAuthor Commented:
I added *.domain.gov.country in the exclusion list by modifying the group policy
The site *.*.gov.* works now - it does not hit proxy and gets resolved internally.

0
 
kumaliAuthor Commented:
OK
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now