Re: Reverse DNS problem


That was not a point. What I've done? I've created
1.168.192.in-addr.arpa reverse zone and made a 204 PTR item in this
zone configuration. And reverse query for 217.98.68.204 started
working! Now we came to my question. Why it works that way? What is a
1.168.192-in-addr.arpa influence on 68.98.217.in-addr.arpa reverse
zone? I could even remove a 68.98.217.in-addr.arpa zone and reverse
queries from internet about 217.98.68.204 still working. It looks like
a DNS server replaces a queries about 217.98.68.0/24 addresses to
according 192.168.1.0/24 addresses and then checking in
1.168.192.in-addr.arpa zone for coresponding PTR item...


On the surface, that doesn't make any since.

What might be causing a problem is the fact that Microsoft's DNS servers are
not designed to configured behind a NATting firewall. Microsoft want you to
place then in a DMZ instead. When you configure a DNS server this way, you
have to go into the Name Servers tab of the properties of each externally
accessible zone and manually add the external FQDNs for your name servers.

For example. Lets assume that my I have two DNS servers. Their NETBIOS names
are NS01 and NS02 while their Internet FQDNs are dns1.mycompany.com and
dns2.mycompany.com.

When I create a primary zone on NS01, the Name Servers tab will
automatically be populated with NS01. I will manually add entries for
dns1.mycompany.com and dns1.mycompany.com using their Internet IPs and then
delete NS01 entry since I don't want the outside world to know anything
about my internal network.

----------
This is only a guess, but maybe the server's NETBIOS name was casing reverse
lookup to fail.

Removing the 68.98.217.in-addr.arpa zone definitely would have an effect.
You must have forgotten to clear your caches before retrying the query.



.

Relevant Pages

  • Re: Find AD hostname from Linux command line
    ... Windows machines cannot register themselves UNLESS they know ... it must happen with your DNS servers for the ZONE of the ... That the DC happens to be the DNS server is merely an accident ... that the reverse mapping "lancelot.ad.mydomain.com" to 192.168.10.11 is ...
    (microsoft.public.win2000.dns)
  • Re: Reverse Lookups
    ... > know about the reverse lookup. ... create that reverse zone on whatever child DNS server is handling those ... specific subnets for your child domain. ... Then allow zone transfers and create ...
    (microsoft.public.win2000.dns)
  • Re: Reverse Lookup (PTR Record) Problem
    ... you can change TTL on the records in reverse ... lookup zone temporarily, to keep it clean. ... PTR records are not being updated/removed correctly. ... Dynamically update DNS A and PTR records for DHCP clients that do not ...
    (microsoft.public.windows.server.dns)
  • Maintaining AD-Integrated Reverse Zone With No DHCP Server on Domain Controller
    ... We had the DHCP server running on the domain controller, ... Apparently the DHCP and DNS applications cooperate with each ... running DHCP on the domain controller, the AD integrated reverse lookup ... domain controller IPs are not appearing in the reverse zone (I had to ...
    (microsoft.public.windows.server.dns)
  • Re: URGENT - DNS Domain name problem
    ... "Herb Martin" wrote: ... >> in the dns server on ns1.domain.org ... >> i have created a a forward lookup zone mydomain.org as a primary zone and ... >> also a reverse lookup zone. ...
    (microsoft.public.windows.server.dns)
Loading