Re: Win2K3 revDNS problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

Does it work for any forward query and fail on any reverse query? Is the
DNS server primary for any reverse zones? Does it fail on these?

--
Greg Lindsay [MSFT]

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

<motzel@xxxxxxxxx> wrote in message
news:1160732973.092041.309530@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,

At the beginning, I'd like to apologise for my bad english, but it's
not my native language.

I have a strange problem with DNS service.

There is a local network 192.168.1.0/24 with internet access through a
router (Cisco 1600). Router translates local adresses to external ones
(let's say xxx.xxx.xxx.0/24) for a few computers (servers).

Computer with address 192.168.1.202 (external xxx.xxx.xxx.204) has a
DNS service running on Windows 2003 SP1. DNS service works without any
problems translating symbolic adresses to numeric, but there is a
problem with opposite direction, but only when I ask server using
external address, for example:

$ host -a xxx.xxx.xxx.204 192.168.1.202

[ everything is ok ]

$ host -a xxx.xxx.xxx.204 xxx.xxx.xxx.202

Trying "204.xxx.xxx.xxx.in-addr.arpa"
;; Got bad packet: bad compression pointer
121 bytes
aa eb 81 83 00 01 00 00 00 01 00 00 03 32 30 34
02 36 38 02 39 38 03 32 31 37 07 69 6e 2d 61 64
64 72 04 61 72 70 61 00 00 0c 00 01 c0 12 00 06
00 01 00 01 4f bc 00 41 08 70 72 69 73 6f 6e 65
72 04 69 61 6e 61 03 6f 72 67 00 0a 68 6f 73 74
6d 61 73 74 65 72 0c 72 6f 6f 74 2d 73 65 72 76
65 72 73 c0 46 77 54 b7 e0 00 00 07 08 00 00 03
84 00 09 3a 80 00 00 01 90

It's very strange for be, because server don't know that it has also
external address (server address is 192.168.1.202, router makes a
translation). It's strange even more, because translating symbolic
addresses to numeric works well regardless of I use local or external
IP address.

So, what is a reason of this problem?

Best Regards,

Bogdan Modzelewski



.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)