Announcement

Collapse
No announcement yet.

dns server problems

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • dns server problems

    Rutherford
    i have a windows 2003 network running in vmware, and i have some questions to ask.

    http://www.facebook.com/album.php?aid=327845&id=509775009&l=1cfee55231

    ive changed the network around a bit but basically on the same subnet i have... Read more

    PC1 - Domain 1 AD (192.168.1.1) mcsenetwork.co.uk

    PC2 - Domain 1 AD replication (192.168.1.2) mcsenetwork.co.uk

    PC3 - Sub Domain 2 AD (192.168.1.3) study2.mcsenetwork.co.uk

    PC4 - Sub Domain 2 Member (192.168.1.4) study2.mcsenetwork.co.uk

    PC5 - Sub Domain 2 Member (192.168.1.5) study2.mcsenetwork.co.uk

    PC6 - Sub Domain 3 AD (192.168.1.6) study1.mcsenetwork.co.uk

    PC7 - Sub Domain 3 Member (192.168.1.7) study1.mcsenetwork.co.uk

    PC8 - Client XP connected to domain 1 (192.168.1. mcsenetwork.co.uk

    PC9 - Client XP connected to domain 2 (192.168.1.9) mcsenetwork.co.uk

    PC10 - Client XP connected to domain 3 (192.168.1.10) mcsenetwork.co.uk

    I have currently a DNS server on PC1, PC3 and PC6 for each domain. PC8 refers in tcpip to dns for DOM1 (192.168.1.1), PC8 refers in tcpip to dns for DOM2 (192.168.1.3), and PC9 refers in tpcip to dns for DOM4 (192.168.1.6).

    Well the roaming profiles work, and i think i still have prob with dns, i took all the client pcs off the network, and attempted reconnecting them, PC8 connects back to the root domain ok, but i cant get PC9 or PC10 back on to DOM2 or 3 respectively. All i get is 'a domain controller for domain study2.mcsenetwork.co.uk could not be contacted'

    i have attempted to create forward and reverse lookup zones for each domain on each dns server, but i think im miissing something

    mcsenetwork.co.uk works fine

    study2.mcsenetwork.co.uk has the following

    FORWARD LOOKUP

    (same as parent folder) Start of authority (SOA) [6], mcsepc3.study2.mcsenetwork
    .co.uk.,hostmaster.study2.mcsenetwork.co.uk

    (same as parent folder) Name Server (NS) mcsepc3.study2.mcsenetwork.co.uk

    mcsepc3 host (A) 192.168.1.3

    mcsepc4 host (A) 192.168.1.4

    mcsepc5 host (A) 192.168.1.5

    mcsepc9 host (A) 192.168.1.9

    REVERSE LOOKUP

    (same as parent folder) Start of authority (SOA) [14], mcsepc3.study2.mcsenetwork.co.uk.,hostmaster.study 2.mcsenetwork.co.uk

    (same as parent folder) Name Server (NS) mcsepc3.study2.mcsenetwork.co.uk

    192.168.1.1 Pointer (PTR) mcsepc1.mcsenetwork.co.uk

    192.168.1.3 Pointer (PTR) mcsepc3.study2.mcsenetwork.co.uk

    192.168.1.4 Pointer (PTR) mcsepc4.study2.mcsenetwork.co.uk

    192.168.1.5 Pointer (PTR) mcsepc5.study2.mcsenetwork.co.uk

    --------------------------

    my nslookup bring back for each machine the following

    PC8 - this conencts to domain ok (this is on msnenetwork.co.uk)

    nsloopup mcsenetwork.co.uk

    Server mcsepc1.mcsenetwork.co.uk

    Address : 192.168.1.1

    Name: study2.mcsenetwork.co.uk

    Address 192.168.1.1

    and

    nsloopup study2.mcsenetwork.co.uk

    Server mcsepc1.mcsenetwork.co.uk

    Address : 192.168.1.1

    *** mcsepc1.mcsenetwork.co.uk can't find study2.mcsenetwork.co.uk: Non-existant domain

    and

    nsloopup study2.mcsenetwork.co.uk

    Server mcsepc1.mcsenetwork.co.uk

    Address : 192.168.1.1

    *** mcsepc1.mcsenetwork.co.uk can't find study1.mcsenetwork.co.uk: Non-existant domain

    looks like this is not finding sub domains study1 and study2

    -------------------------------

    PC9 - doesnt connect to domain

    nsloopup mcsenetwork.co.uk

    Server mcsepc3.mcsepc2.mcsenetwork.co.uk

    Address : 192.168.1.3

    *** mcsepc3.study2.mcsenetwork.co.uk can't find mcsenetwork.co.uk: Non-existant domain

    and

    nslookup study1.mcsenetwork.co.uk

    Server mcsepc3.mcsepc2.mcsenetwork.co.uk

    Address : 192.168.1.3

    *** mcsepc3.study2.mcsenetwork.co.uk can't find study1.mcsenetwork.co.uk: Non-existant domain

    and

    nslookup study2. mcsenetwork.co.uk

    Server mcsepc3.study2.mcsenetwork.co.uk

    Address : 192.168.1.3

    Name: study2.mcsenetwork.co.uk

    -----------------------

    PC10

    nslookup mcsenetwork.co.uk

    Server mcsepc6.study1.mcsenetwork.co.uk

    Address : 192.168.1.6

    *** mcsepc6.study1.mcsenetwork.co.uk can't find mcsenetwork.co.uk: Non-existant domain

    and

    nslookup study1.mcsenetwork.co.uk

    Server mcsepc3.study1.mcsenetwork.co.uk

    Address : 192.168.1.6

    Name: study1.mcsenetwork.co.uk

    and

    nslookup study2.mcsenetwork.co.uk

    Server mcsepc6.study1.mcsenetwork.co.uk

    Address : 192.168.1.6

    *** mcsepc6.study1.mcsenetwork.co.uk can't find study2.mcsenetwork.co.uk: Non-existant domain

    ------------------------------------

    can anyone help me should each subdomain tcpip be pointing the the root dns server mcsenetwork.co.uk for dns resolving. i dunno im lost, and help appreciated, thanks.

    whats the best way to do dns on subdomains, and how do i set it up so root domains can resolve them, and sub domains can resolve other subdomains, by resolving root domain, im not sure the best way of doing this,.

  • #2
    Re: dns server problems

    it looks like the client ive tried to add works with

    study2, but not with the full domain name study2.mcsenetwork.co.uk

    this i believe is a dns problem, can anyone advise what to check, i think maybe i have other problems to, thanks


    if i configure that pc9 and 10 to use the dns server of 192.168.1.1 (root domain), i can connect to the domain study2 without any problems
    Last edited by alienkidmj12; 24th October 2009, 16:20.

    Comment


    • #3
      Re: dns server problems

      i'll be honest - i found it really hard to read and understand, so i scanned over it.

      however, here's a suggestion.

      Each device should have two name servers configured. If it's got DNS installed, it should point to itself. Otherwise, it should point to the DNS server for it's LOCAL domain. THe second DNS server it should point to should be the forest root.

      Each DNS SERVER should have a 'forwarder' configured to the top of the forest.
      the top of the forest should have a stub zone for each domain.

      I could be wrong.. but that;s a guess
      Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

      Comment

      Working...
      X