In scuba_jeff <
[email protected]> posted a question
Then Kevin replied below:
: "Ace Fekay [MVP]"
: message :: In :: scuba_jeff <
[email protected]> posted their thoughts, then I offered
:: mine
::: we recently changed ip address's for the parent domain and all
::: seemed to be working fine, communication and replication from parent
::: (Northville.com) to child (termnial.northville.com) users were able
::: to log in to either domain and share resources like their supposed
::: to. yesterday we get a call from a user who cannot log int a server
::: in the parent domain with her child domain login id, error is
::: system cannot log you in because domain TERMINAL is not avaible-
::: but users form the parent CAN login into the child servers.
:::
::: To make a long story kinda short in the parent domains DNS records
::: there are no SRV recordes for the child domain and dynamic updates
::: ot the parent have stopped?
:::
::: the servers still apper in ad sites and servers.
::: the child domain is located on the other side of a wan but in the
::: same site
:::
::: any clue where to turn would be helpful
:::
::: jeff
::
:: What was the latest thing that was changed prior to this, say in the
:: past 3 weeks? Maybe SP4 installed?
::
:: We'll need more info on your topology and your DCs, and if you have
:: any delegations.
::
:: Some things to look for when SRVs are missing and it was working,
:: but now it's not and you just changed IP addresses.....
::
:: 1. Use of your ISP's DNS in your machines' (DCs and clients) IP
:: properties. Can't use them.
:: 2. SIngle label DNS domain name and SP4.
:: 3. Wrong IP for DNS address...
:: 4. DNS server listening on wrong IP
:: 5. Check nameserver tab to insure you properly changed to the new IPs
::
::
::
::
:: --
:: Regards,
:: Ace
::
:: Please direct all replies to the newsgroup so all can benefit.
:: This posting is provided "AS IS" with no warranties.
::
:: Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
:: Microsoft Windows MVP - Active Directory
:
: I have a parentdomain with 3 domain controllers (northville.com) and a
: child domain with 2 domain controllers (terminal.northville.com)
:
: Here are the answers to your questions
:
: 1. Use of your ISP's DNS in your machines' (DCs and clients) IP
: properties.
:
: Not using them , child domain controllers dns primary points to it
: self the secondary to the parent domain controller. the names can be
: resolved from child to to parent and user can log in from child to
: parent not from parent TO child
:
: 2. SIngle label DNS domain name and SP4.
:
: NO , fully qualified domains - northville.com and
: terminal.northville.com sp3 on all dc's
:
: 3. Wrong IP for DNS address...
:
: I can ping the servers by Name
:
: 4. DNS server listening on wrong IP
:
: Dns set to listen on all address by default
:
: 5. Check nameserver tab to insure you properly changed to the new IPs
:
: checked already
:
: all tests pass on dcdiag
: here are the results form netdiag on a child domain controller
:
: All tests passed here is relevent info, dns test is reflecting my
: problem
: but the entrys never register. I ran ipconfig /registerdns and stopped
: and restarted netlogon on child doman controller but no help. I am
: leary of doing it to the parent domain controller as i dont want
: anything to get worse
:
:
: Netcard queries test . . . : Passed
:
: Host Name. . . . . . . . . : HOLTSVDC01
: IP Address . . . . . . . . : 192.168.114.5
: Subnet Mask. . . . . . . . : 255.255.255.0
: Default Gateway. . . . . . : 192.168.114.6
: Dns Servers. . . . . . . . : 192.168.114.5
: 192.168.100.10
:
: DNS test . . . . . . . . . . . . . : Passed
: PASS - All the DNS entries for DC are registered on DNS server
: '192.168.114.
: 5' and other DCs also have some of the names registered.
: [WARNING] The DNS entries for this DC are not registered correctly
: on DNS se
: rver '192.168.100.10'. Please wait for 30 minutes for DNS server
: replication.
On the Parent DNS in the northville.com zone create a delegation named
terminal then point that delegation to the names and IP addresses of the
Child DNS servers.
The child DNS server should have a forwarder to the parent DNS and the box
"Do not use recursion" should have a check in it.
