June 18 One more doubt regarding reverse look up please

  • Thread starter Thread starter PA
  • Start date Start date
P

PA

Thanks a lot Ace FeKay. This is my third post of the day
and I appreciate your prompt response.

As you rightly said I was looking at Advanced tab of the
DNS menu where I saw ./ root file. Now I think I have
figured out it is a reverse look up issue which is causing
problems and preventing users from accesssing many web
sites. Can you Please tell me the implications behind
deleting a reverse look up. I am nervous and do not want
to mess up on my first job. Also right now the previous
admin has set reverse look up like this.

I feel Syntax is wrong 192.168.1.1 X subnet

I thought it should have syntax of in-addrp

Please point me in the right direction

THANKS A TON.............
 
PA said:
Thanks a lot Ace FeKay. This is my third post of the day
and I appreciate your prompt response.

As you rightly said I was looking at Advanced tab of the
DNS menu where I saw ./ root file. Now I think I have
figured out it is a reverse look up issue which is causing
problems and preventing users from accesssing many web
sites.

No, the use of or lack or REVERSE zone will almost never
have any effect on web browsing by your users.

(It might on a VERY RARE site prevent certain file downloads,
or cause problems with email transfers between SERVERS, but
it isn't going to affect the users ability to visit yahoo.com or
dell.com or most any other site.)
Can you Please tell me the implications behind
deleting a reverse look up. I am nervous and do not want
to mess up on my first job. Also right now the previous
admin has set reverse look up like this.

Why did you create the reverse zone? If you had a reason,
most people do not, then it will stop that functionality.

INTERNAL reverse zones, especially for private address
ranges almost never hurt or help you.
I feel Syntax is wrong 192.168.1.1 X subnet

It is, the convention is to reverse the octets in the reverse
zone NAME, so that 192.168.0.0 become 168.192.in-addr.arpa.

And 192.168.48.0 become 48.168.192.in-addr.arpa.

I thought it should have syntax of in-addrp

The names DISPLAYED by the Microsoft GUI, in an effort
to be helpful, are confusing however.
Please point me in the right direction

You have another problem (besides) reverse lookup or reverse
zone.

What is your REAL problem -- let us help you solve that?

Earlier you mention the cache -- you don't need to mess with that
and if you do, just CLEAR it and let it reload.

My GUESS -- pure guess -- is you have not forwarded your
internal DNS to an appropriate external DNS server and you
internal DNS is not configured to do the actual recursion.

Now if you have an ACTUAL ZONE named ".", that is what
is stopping external requests -- it prevents the internal server
from searching the INTERNET root down, and it disables
forwarders so it cannot hand off the job.

If you have a "." zone...
DELETE the (real) DOT "." zone. Set your DNS server's
forwarder tab to your ISP (or your firewall DNS server).

Do not worry about anything in the cache -- unless you feel
it is corrupted and then you can just restart the server or clear the
cache.
 
In
PA said:
Thanks a lot Ace FeKay. This is my third post of the day
and I appreciate your prompt response.

As you rightly said I was looking at Advanced tab of the
DNS menu where I saw ./ root file. Now I think I have
figured out it is a reverse look up issue which is causing
problems and preventing users from accesssing many web
sites. Can you Please tell me the implications behind
deleting a reverse look up. I am nervous and do not want
to mess up on my first job. Also right now the previous
admin has set reverse look up like this.

I feel Syntax is wrong 192.168.1.1 X subnet

I thought it should have syntax of in-addrp

Please point me in the right direction

THANKS A TON.............


Just as Herb said, your issue is NOT a reverse zone issue. It's something
else. As for the reverse syntax, as Herb said, the GUI shows it to you that
way. If you look at the actual file, it's in the in-addr.arpa format.

Relax dude, have a cold beer or something.

As for accessing websites, what version of Windows is this? If it's W2k3, it
may be an EDNS0 issue.

Maybe using a different forwarder will take care of the problem. Try
4.2.2.2. That works fine.



--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top