K
kidem
Is there a way to get back my _msdcs.domain.com zone, some one deleted it?
H
Herb Martin
kidem said:
You can just re-create it (and if a separate zone
make it dynamic.)
Here are some general hints on DNS for AD but
they include how to get the names registered and
a link to a KB article that (IIRC) talks about manually
fixing it:
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)
netdiag /fix
....or maybe:
dcdiag /fix
(Win2003 can do this from Support tools):
nltest /dsregdns /server
C-ServerNameGoesHerehttp://support.microsoft.com/kb/q260371/
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
K
kidem
wow...i thought it be more complicated than that, from past exp with 2000.
this is 2003 and it worked thanks
this is 2003 and it worked thanks
Herb Martin said:kidem said:
You can just re-create it (and if a separate zone
make it dynamic.)
Here are some general hints on DNS for AD but
they include how to get the names registered and
a link to a KB article that (IIRC) talks about manually
fixing it:
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)
netdiag /fix
...or maybe:
dcdiag /fix
(Win2003 can do this from Support tools):
nltest /dsregdns /server
http://support.microsoft.com/kb/q260371/
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
H
Herb Martin
kidem said:
Glad to help...
Which method(s) did you use?
--
Herb Martin
Herb Martin said:kidem said:
You can just re-create it (and if a separate zone
make it dynamic.)
Here are some general hints on DNS for AD but
they include how to get the names registered and
a link to a KB article that (IIRC) talks about manually
fixing it:
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)
netdiag /fix
...or maybe:
dcdiag /fix
(Win2003 can do this from Support tools):
nltest /dsregdns /server
http://support.microsoft.com/kb/q260371/
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
K
kidem
i recreated it, _msdcs.domain.com , which everything showed up, then did a
netdiag /fix just for GP...
netdiag /fix just for GP...
Herb Martin said:kidem said:
Glad to help...
Which method(s) did you use?
--
Herb Martin
Herb Martin said:Is there a way to get back my _msdcs.domain.com zone, some one deleted
it?
You can just re-create it (and if a separate zone
make it dynamic.)
Here are some general hints on DNS for AD but
they include how to get the names registered and
a link to a KB article that (IIRC) talks about manually
fixing it:
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)
netdiag /fix
...or maybe:
dcdiag /fix
(Win2003 can do this from Support tools):
nltest /dsregdns /server
http://support.microsoft.com/kb/q260371/
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
K
kidem
im seeing another problem, from newly promoted DC i can replicate through
Sites and services fine, but from first DC i can not, gives error such as
object is being removed and something about naming context, sorry i dont
remember the exact error!!
Any ideas?
Sites and services fine, but from first DC i can not, gives error such as
object is being removed and something about naming context, sorry i dont
remember the exact error!!
Any ideas?
kidem said:i recreated it, _msdcs.domain.com , which everything showed up, then did a
netdiag /fix just for GP...
Herb Martin said:kidem said:
Glad to help...
Which method(s) did you use?
--
Herb Martin
Is there a way to get back my _msdcs.domain.com zone, some one deleted
it?
You can just re-create it (and if a separate zone
make it dynamic.)
Here are some general hints on DNS for AD but
they include how to get the names registered and
a link to a KB article that (IIRC) talks about manually
fixing it:
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)
netdiag /fix
...or maybe:
dcdiag /fix
(Win2003 can do this from Support tools):
nltest /dsregdns /server
http://support.microsoft.com/kb/q260371/
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
H
Herb Martin
kidem said:
It's usually a DNS problem, but usually the
worst case is that you remove AD from the
messed up DC (DCPromo maybe with the
/forceremoval switch) and then optionally
put it back (DCPromo again.)
Here's DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)
netdiag /fix
....or maybe:
dcdiag /fix
(Win2003 can do this from Support tools):
nltest /dsregdns /server
C-ServerNameGoesHerehttp://support.microsoft.com/kb/q260371/
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]