• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

DHCP & DNS

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

    #11
    Originally posted by Dr Evil
    If it's 2000 or 2003 it will query DNS for the DC to login to.
    Either way your DHCP scope is pointing at the router as DNS.
    . . . or is that too obvious?...
    Perhaps "006 - DNS Servers - 192.168.1.10 - 81.x.x.x 81.x.x.x" is untidy?

    Remove the 81.* DNS servers. Clients will then direct all name queries to the DNS Server at 192.168.1.10. It will then answer all queries directly for clients for the domain it is authoritative for (i.e. Blah.local).

    If it doesn't know about a domain it can (in order of best practise):

    [1]
    resolve it via 192.168.1.5 (which is, I assume, another caching DNS server built into the router - it will usually have DNS data from the ISP's DHCP).

    [2]
    resolve it via the ISP DNS servers - you need to tell 192.168.1.10 what they are.

    [3]
    resolve directly using the root servers.

    Comment


      #12
      Another thing to add - especially about the 'slowness' of logon: it's most likely to be problems with reverse DNS (IP to name mapping). Make sure in-addr.arpa is correctly configured.

      Try nslookup too, clients should display 192.168.1.10 and 192.168.1.10 itself should display 127.0.0.1.

      "arp -a" is useful too!

      Comment


        #13
        Thanks guys,

        It's all sorted.

        Rokie mistakes - I've done this about 50 times before

        I'd not set the scope - duh

        When I setup the server I'd taken for granted that the router's address was 192.168.1.1 - It was infact 192.168.1.5 - When I changed it onsite I'd missed changing one setting.
        Throw them to the lions - WC2 5.4

        Comment


          #14
          Originally posted by wc2
          Thanks guys,

          It's all sorted.

          Rokie mistakes - I've done this about 50 times before

          I'd not set the scope - duh

          When I setup the server I'd taken for granted that the router's address was 192.168.1.1 - It was infact 192.168.1.5 - When I changed it onsite I'd missed changing one setting.
          I still want to be paid for my effort. If you don't have my money for me I'll crack your fuc*ing head wide open in front of everybody in the bank. And just about the time that I'm coming out of jail, hopefully, you'll be coming out of your coma. And guess what? I'll split your fuc*ing head open again, 'cause I'm fuc*ing stupid. I don't give a fuc* about jail, that's my business, that's what I do.

          Comment


            #15
            Frankly, I'm disgusted . . . .
            "The Kop's exclusive, an institution, and if you're a member of the Kop you feel you're a member of a society, you've got thousands of friends around you and they're united and loyal"

            Comment

            Working...
            X