How to create domain controller in Linux for windows client?

Linux and Unix-Like Red Hat
1

Hi Team
I have configured a linux dns server locally. Its fully working on linux clients but not windows client as its can't ping host by name. someone told me to create domain controller for working this to windows client as well.
I am new in linux and not aware how to create the domain and add the windows client to this domain.
DNS server name=server.example.com

Can anyone explain how to get this? I am totally stucked here.

Thanks in Advance

2

Is the windows client aware of that local DNS- server?

3

Yes. Nslookup is working for the host by IP but not by hostname. That's the main issue here.

4

Hi Boby,

I believe the DHCP is independent service to provide IP Address.
can you check primary DNS server settings on windows client.
Can you validate reverse and forward lookup from Linux client machines and verify in windows same.
Can you check the nslookup with connecting to you DHCP server. nslookup should independent to OS this should resolve.

Hope this narrow down the issue.

Regards
Tarun.

5

On one of your Linux clients look at /etc/resolv.conf
You must provide the same information to your Windoz clients. If they get their IP from a DHCP server, it is sufficient to add the DNS information to the DHCP data.

6

Static Ip is assigned to windows client here, no DHCP.
Above the things is working as well.

Can you please trace the below log captured from windows client...

C:\Users\hitpc>nslookup server
Server:  server.rncihspa.com
Address:  10.20.30.15

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to server.rncihspa.com timed-out


C:\Users\hitpc>nslookup 10.20.30.15
Server:  server.rncihspa.com
Address:  10.20.30.15

Name:    server.rncihspa.com
Address:  10.20.30.15


C:\Users\hitpc>ping 10.20.30.15

Pinging 10.20.30.15 with 32 bytes of data:
Reply from 10.20.30.15: bytes=32 time<1ms TTL=63
Reply from 10.20.30.15: bytes=32 time<1ms TTL=63

Ping statistics for 10.20.30.15:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\hitpc>ping -a 10.20.30.15

Pinging server.rncihspa.com.154.127.10.in-addr.arpa [1
ytes of data:
Reply from 10.20.30.15: bytes=32 time=314ms TTL=63
Reply from 10.20.30.15: bytes=32 time<1ms TTL=63
Reply from 10.20.30.15: bytes=32 time<1ms TTL=63

Ping statistics for 10.20.30.15:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 314ms, Average = 104ms


C:\Users\hitpc>ping server
Ping request could not find host server. Please check the name and try again.


C:\Users\hitpc>nslookup -debug server
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 1, rcode = NOERROR
        header flags:  response, auth. answer, want recursion, recursion a
        questions = 1,  answers = 1,  authority records = 1,  additional =

    QUESTIONS:
        15.30.20.10.in-addr.arpa, type = PTR, class = IN
    ANSWERS:
    ->  15.30.20.10.in-addr.arpa
        name = server.rncihspa.com
        ttl = 86400 (1 day)
    AUTHORITY RECORDS:
    ->  30.20.10.in-addr.arpa
        nameserver = server.rncihspa.com
        ttl = 86400 (1 day)
    ADDITIONAL RECORDS:
    ->  server.rncihspa.com
        internet address = 10.20.30.15
        ttl = 86400 (1 day)

------------
Server:  server.rncihspa.com
Address:  10.20.30.15

DNS request timed out.
    timeout was 2 seconds.
timeout (2 secs)
DNS request timed out.
    timeout was 2 seconds.
timeout (2 secs)
*** Request to server.rncihspa.com timed-out

I think it has the enough to get what we are looking..

Thanks

7

Boby,

I) can you add "DNS suffix for this connection" as your "rncihspa.com" in windows LAN card IPv4 properties and then on Advanced DNS tab.

and then check the ping status.

II) Can you check nslookup for other SRV or A records in DNS instead of server host.

8

I have already added DNS suffix to lan card. Same issue is with other srv.

9

Anyone has any update the same...