DNS errors

  • Thread starter Thread starter wayne
  • Start date Start date
W

wayne

I have a new customer who had another company set up
their wondows 2000 domain. The DNS has 2 forward lookup
zones.

server.domainname.org

1: . (dot) forward zone
with 2 folders
ARPA and ORG

2: domainname.org
with 3 folders
_msdcs, _sites and _tcp

1 reverse lookup zone

192.168.2.x

All zones are set to allow dynamic updates

in network neighborhood only the servers appear no
workstations. I have entered the DNS address in the
workstation settings and then the workstations will show
up in the network neighborhood but not in DNS.

I tested the DNS in NSLOOKUP and the server resolves fine.

in the system log I recive the followinf errors

Event Type: error
Event Source: NETLOGON
Event category: none
Event ID: 5774
user: N/A
Computer: server
Description: registration of the DNS
record '_ldap._tcp.dc._msdcs.domainname.org. 600 IN SRV 0
100 389 server.domainame.org' failed with the following
error: DNS server unable to interpret format. Data: 0000:
29 23 00 00 )#..

also get 6 other errors simular to the first

_ldap._tcp.default-first-
sitename._sites.dc._msdcs.domainname.org 600 in srv 0 100
389 server.domainname.org

_kerberos._tcp.domainname.org 600 in srv 0 100 88
server.domainname.org

_kerbros._tcp.default-first-site-
name._sites.domainname.org 600 in srv 0 100 88
server.domainname.org

_kpasswd.udp.domainname.org. 600 in srv 0 100 464
server.domainame.org

_kerberos._udp.doaminname.org 600 in srv 0 100 88
server.domainame.org

_gc._tcp.doaminname.org 600 in srv 0 100 3268
server.domainname.org

their is a mitel networks SME server 5.6 as a member of
the domain it does not have its own DNS but must be
pointed to another server fo its DNS needs

how do i fix this without doing the server over from
scratch?
 
In
wayne said:
I have a new customer who had another company set up
their wondows 2000 domain. The DNS has 2 forward lookup
zones.

server.domainname.org

1: . (dot) forward zone
with 2 folders
ARPA and ORG

2: domainname.org
with 3 folders
_msdcs, _sites and _tcp

1 reverse lookup zone

192.168.2.x

All zones are set to allow dynamic updates

in network neighborhood only the servers appear no
workstations. I have entered the DNS address in the
workstation settings and then the workstations will show
up in the network neighborhood but not in DNS.

I tested the DNS in NSLOOKUP and the server resolves fine.

in the system log I recive the followinf errors

Event Type: error
Event Source: NETLOGON
Event category: none
Event ID: 5774
user: N/A
Computer: server
Description: registration of the DNS
record '_ldap._tcp.dc._msdcs.domainname.org. 600 IN SRV 0
100 389 server.domainame.org' failed with the following
error: DNS server unable to interpret format. Data: 0000:
29 23 00 00 )#..

also get 6 other errors simular to the first

_ldap._tcp.default-first-
sitename._sites.dc._msdcs.domainname.org 600 in srv 0 100
389 server.domainname.org

_kerberos._tcp.domainname.org 600 in srv 0 100 88
server.domainname.org

_kerbros._tcp.default-first-site-
name._sites.domainname.org 600 in srv 0 100 88
server.domainname.org

_kpasswd.udp.domainname.org. 600 in srv 0 100 464
server.domainame.org

_kerberos._udp.doaminname.org 600 in srv 0 100 88
server.domainame.org

_gc._tcp.doaminname.org 600 in srv 0 100 3268
server.domainname.org

their is a mitel networks SME server 5.6 as a member of
the domain it does not have its own DNS but must be
pointed to another server fo its DNS needs

how do i fix this without doing the server over from
scratch?
Click to expand...

What would really help is an ipconfig /all but my guess is you have
yourISP's DNS in your NIC for DNS, when you should have only the DCs address

Then you need to remove the "." Forward lookup zone to allow your DNS to
resolve internet names. You can also enable forwarders and put your ISP's
DNS in.
 
-----Original Message-----
In

What would really help is an ipconfig /all but my guess is you have
yourISP's DNS in your NIC for DNS, when you should have only the DCs address

Then you need to remove the "." Forward lookup zone to allow your DNS to
resolve internet names. You can also enable forwarders and put your ISP's
DNS in.





.
Click to expand...

Yes the nic has 2 DNS entries for the ISP and an entry
for its self. the servers IP address is first in the list
followed by the ISP's dns addresses.

what effect will removing the "." forward lookup zone
have?
 
In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
Yes the nic has 2 DNS entries for the ISP and an entry
for its self. the servers IP address is first in the list
followed by the ISP's dns addresses.
Click to expand...

You *MUST* remove the ISP's DNS, period.
what effect will removing the "." forward lookup zone
have?
Click to expand...
It will make your DNS server resolve internet names.
Read this 300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1
 
Remove the "." root zone and point the DNS server to itself ONLY for DNS. All clients that are members of this domain should
also only point at this DC for DNS.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.
 
-----Original Message-----
Remove the "." root zone and point the DNS server to
Click to expand...
itself ONLY for DNS. All clients that are members of
this domain should
also only point at this DC for DNS.

Thank you,
Mike Johnston
Microsoft Network Support
Click to expand...
confers no rights. Use of included script samples are
subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all
Click to expand...
responses to this message are best directed to the
newsgroup/thread from
which they originated.



.
Click to expand...

I removed ISP's dns addresses from tcp/ip and entered
only the dns servers ip address. added the isp's dns
ipaddress to the forwarders in the dns server nad deleted
the "." root zone.

The errors stopped and I can get to the internet.

on a few workstations I am experiencing somthing weird. I
can not browse the network neighborhood even though their
are mapped drives to the server. I can only log on the
the domain as the user of the workstation. I can not log
in as administrator it tells me "the system cannot log
you on now because the domain domainname is not available"

this happens on 2 workstations a win2k and a winxp
workstation. these same 2 workstations also do not show
up on the dns server and can not be resolved
 
In
wayne said:
itself ONLY for DNS. All clients that are members of
this domain should
confers no rights. Use of included script samples are
subject to the
responses to this message are best directed to the
newsgroup/thread from

I removed ISP's dns addresses from tcp/ip and entered
only the dns servers ip address. added the isp's dns
ipaddress to the forwarders in the dns server nad deleted
the "." root zone.

The errors stopped and I can get to the internet.

on a few workstations I am experiencing somthing weird. I
can not browse the network neighborhood even though their
are mapped drives to the server. I can only log on the
the domain as the user of the workstation. I can not log
in as administrator it tells me "the system cannot log
you on now because the domain domainname is not available"

this happens on 2 workstations a win2k and a winxp
workstation. these same 2 workstations also do not show
up on the dns server and can not be resolved
Click to expand...
The Network Neighborhood is another issue altogether, because nethood uses
NetBIOS you have to enable NetBIOS over TCP/IP on the WINS tab.
Have you verified these clients are using the DC for DNS only?
 
Back
Top